Redesigning Account Management Workflows
Fixing visibility gaps and handoff friction across Sales, Finance, CX, and Ops
The Problem
01
No shared view of the account lifecycle across three core systems (e.g., Salesforce, NetSuite, Sky) > duplicated work and blind spots.
02
Terminology drift across teams (Sales vs. Finance vs. Ops) caused misinterpretation and rework.
03
Backstage work (hardware/installation/onboarding coordination) wasn’t represented handoffs broke down.
04
Approval latency grew due to missing key-data prompts at critical gates.
My Approach
Discovery → Modeling → Validation
Discovery & Alignment
- Stakeholder mapping
- Tool/data audit
- Shared vocabulary
Modeling Complexity
- Archetypes
- Macro/micro journeys
- Failure points & gates
System Insight & Validation
- Service blueprint v1
- Moderated tasks on Figma
- Prioritized recs
Phase 1: Discovery & Alignment
- Mapped stakeholders and tooling across Sales/AM, Finance, CX, Technical, Ops; audited data/handoffs
- Created a shared vocabulary to reduce terminology drift.
- Outcome: Confirmed 3-system fragmentation and missing prompts at critical checkpoints.
Modeling Complexity
I defined internal actor archetypes and built macro/micro journeys to surface failure points, checkpoints, and invisible backstage work.
Outcome:
We pinpointed where handoffs break and which checkpoints need prompts or checklists.
Phase 2:
Phase 3:
System Insight & Validation
I drafted service blueprint and tested the proposed flows with 5–7 people (success = task completion without help). I then rewrote labels and added prompts where they hesitated.
Outcome: Final recommendations were prioritized with Ops/Finance owners.
Finding to Decision #1
Data completeness at a critical checkpoint
Finding to Decision #2
Terminology drift
Finding to Decision #3
Handoff gaps
- Finding: Same data was entered twice and still incomplete at a critical checkpoint across System A/B/C.
- Decision: Add required key-data prompts at that checkpoint and align labels across System A/B/C.
- Expected impact: Raise data completeness toward 95%+ and reduce rework tickets.
- Finding: Different teams used different names for the same step (terminology drift).
- Decision: Publish a shared glossary and update UI copy/tooltips to match it.
- Expected impact: Fewer crossed wires during approvals and fewer back-and-forths.
- Finding: Backstage steps were invisible during the Sales/AM → Onboarding handoff.
- Decision: Create a blueprint handoff checklist with clear owners at each step.
- Expected impact: Shorter time-to-activation and fewer hand-backs.
Illustrative, anonymized checklist aligned with the blueprint pilot.
🔒 Note on Confidentiality
Due to the sensitive nature of this project, all visuals, personas, and system references have been abstracted. This case study focuses solely on methodology and process to demonstrate research leadership, systems thinking, and stakeholder alignment.




