From business need to Salesforce design.

01 · Business challenge

Leads enter through spreadsheets, email and WhatsApp. Ownership is agreed informally, duplicate records appear, follow-up is inconsistent and managers cannot see a dependable pipeline.

02 · Discovery & analysis

I would interview sales representatives, the sales manager, operations and a CRM admin. Key questions: Where does each lead come from? What defines a territory? Who owns a lead with missing location? When must contact happen? What signals qualification?

Current state: no single point of ownership or reliable status history.

03 · Requirements

• Functional: capture a source and region, route a new lead, create a follow-up task, surface overdue work, and report on lead age and conversion.
• Business rules: Lagos and Abuja route to their sales queues. Unknown regions route to triage. Urgent leads get a shorter response target.
• Non-functional: only authorized users can edit assignment rules; report data must be consistently populated and accessible.

04 · Solution & rationale

Use standard Lead and Opportunity objects before introducing custom objects. Assignment rules handle territory ownership; Flow creates tasks and alerts; duplicate rules prompt review; validation rules protect required qualification data. Dashboards show aging, source, conversion and stalled opportunities.

05 · Implementation, test & adoption

Configure lead fields, queues, rules, Flow, duplicate management and reports in a sandbox. Migrate cleansed sample leads only after mapping and validation. UAT covers each region, unknown locations, urgent leads, duplicates, task due dates and permissions. Train sales users on a simple daily queue view and managers on exception handling.

06 · Expected value & reflection

Projected, not measured: clearer ownership, faster response, fewer missed leads and more trustworthy pipeline reporting. A risk is routing based on incomplete location data, so triage and monitoring remain essential. I would review queue backlog and user feedback after launch before adding complexity.

01 · Business challenge

Ad hoc profile changes have made access inconsistent. Relationship managers need their own client records, team leads need portfolio oversight and compliance reviewers need read access to selected fields without editing rights.

02 · Discovery & analysis

I would review job responsibilities with business leads, compliance and the Salesforce admin. I would inventory objects, fields, record ownership and current permissions, then document who must read, create, edit, approve or export each type of information.

03 · Requirements

• Functional: relationship managers access assigned clients; leads see team portfolios; reviewers have read-only access to approved records.
• Security rules: sensitive fields remain hidden unless role duties require them; elevated permissions are assigned through named permission sets.
• Non-functional: access changes need an owner, approval, review cadence and test evidence.

04 · Solution & rationale

Start with restrictive organization-wide defaults, then use role hierarchy, sharing rules and permission sets for documented exceptions. Apply field-level security separately from record sharing. Avoid a profile for every job variation; permission sets make specific grants easier to review.

05 · Implementation, test & adoption

Build an access matrix before configuration. Test with representative users, including negative tests for records and fields that must stay hidden. Validate reports, list views, exports and API-connected users. Train managers on access requests and schedule periodic permission reviews.

06 · Expected value & reflection

Projected, not measured: clearer accountability, fewer excessive grants and simpler access reviews. Least privilege may slow some collaboration, so I would document legitimate sharing exceptions and measure support tickets after release.