Understanding users and the whole problem
11 min read
Lesson objectives
- Diagnose the user problem across channels, compare alternatives, and produce a traceable recommendation.
For the user problem across channels, the consultant faces this condition: a web form improves, yet users still visit a branch because later evidence requirements remain unclear. The decision is not a technology selection; it is which explanation deserves investment. Inputs are user research, channel analytics, abandonment logs, journey maps, and accessibility needs. The work record separates each observation from its hypothesis and asks for disconfirming evidence before scope is fixed. The executable output is a need-based problem statement and journey map linking pain points to causes and owners, accepted only when another sponsor can trace evidence to criterion and then to decision.
| Evidence | Validity test | Conflict test | Use rule |
|---|---|---|---|
| user research | Explains context and motivation, but needs an operating record to estimate prevalence. | Compare it with channel analytics; explain agreement or conflict. | Use it in a need-based problem statement and journey map linking pain points to causes and owners only to the extent that it supports end-to-end task completion rather than screen completion alone. |
| channel analytics | Adds an independent view; state what it supports and what remains outside its scope. | Compare it with abandonment logs; explain agreement or conflict. | Use it in a need-based problem statement and journey map linking pain points to causes and owners only to the extent that it supports end-to-end task completion rather than screen completion alone. |
| abandonment logs | Adds an independent view; state what it supports and what remains outside its scope. | Compare it with journey maps; explain agreement or conflict. | Use it in a need-based problem statement and journey map linking pain points to causes and owners only to the extent that it supports end-to-end task completion rather than screen completion alone. |
| journey maps | Explains context and motivation, but needs an operating record to estimate prevalence. | Compare it with accessibility needs; explain agreement or conflict. | Use it in a need-based problem statement and journey map linking pain points to causes and owners only to the extent that it supports end-to-end task completion rather than screen completion alone. |
| accessibility needs | Adds an independent view; state what it supports and what remains outside its scope. | Compare it with exception records; explain agreement or conflict. | Use it in a need-based problem statement and journey map linking pain points to causes and owners only to the extent that it supports end-to-end task completion rather than screen completion alone. |
| exception records | Shows a performance pattern when definition, period, and case mix are stable. | Compare it with stakeholder observations; explain agreement or conflict. | Use it in a need-based problem statement and journey map linking pain points to causes and owners only to the extent that it supports end-to-end task completion rather than screen completion alone. |
| stakeholder observations | Explains context and motivation, but needs an operating record to estimate prevalence. | Compare it with user research; explain agreement or conflict. | Use it in a need-based problem statement and journey map linking pain points to causes and owners only to the extent that it supports end-to-end task completion rather than screen completion alone. |
| Alternative explanation | What it explains | Discriminating test | What weakens it |
|---|---|---|---|
| Technology | Explains change in user research without change in channel analytics. | Isolate the component and observe end-to-end task completion rather than screen completion alone. | Weakened if a web form improves, yet users still visit a branch because later evidence requirements remain unclear after isolation. |
| Process | Explains waiting between channel analytics and abandonment logs. | Measure value time and exceptions for the user problem across channels. | Weakened when no handoff or rework exists. |
| Data | Explains conflict between user research and stakeholder observations. | Align definition, sample, and refresh before a need-based problem statement and journey map linking pain points to causes and owners. | Weakened when lineage agrees while the effect persists. |
| Incentives | Explains behaviour that reduces end-to-end task completion rather than screen completion alone despite available tools. | Compare team targets with resource decisions in: a web form improves, yet users still visit a branch because later evidence requirements remain unclear. | Weakened across differently rewarded teams with similar behaviour. |
| Judgment | Prefer the the user problem across channels explanation with the fewest hidden assumptions. | Record confidence, disconfirming evidence, and the next test. | Does not justify an irreversible commitment. |
| Option | Decisive criterion | Required evidence | Decision rule |
|---|---|---|---|
| polishing the interface | task completion | Test its effect on end-to-end task completion rather than screen completion alone with user research. | Continue only when it supports a need-based problem statement and journey map linking pain points to causes and owners without breaching risk tolerance. |
| automating the form | burden | Test its effect on end-to-end task completion rather than screen completion alone with channel analytics. | Continue only when it supports a need-based problem statement and journey map linking pain points to causes and owners without breaching risk tolerance. |
| redesigning the end-to-end journey around user need | inclusion | Test its effect on end-to-end task completion rather than screen completion alone with abandonment logs. | Continue only when it supports a need-based problem statement and journey map linking pain points to causes and owners without breaching risk tolerance. |
| a bounded reversible test | dependencies | Test its effect on end-to-end task completion rather than screen completion alone with journey maps. | Continue only when it supports a need-based problem statement and journey map linking pain points to causes and owners without breaching risk tolerance. |
| Criterion | Operational definition | Rating source | Sensitivity test |
|---|---|---|---|
| task completion | Define it through the user problem across channels, not a promotional adjective. | Rate from user research in the condition where a web form improves, yet users still visit a branch because later evidence requirements remain unclear. | Vary the weight and test whether a need-based problem statement and journey map linking pain points to causes and owners remains preferred. |
| burden | Define it through the user problem across channels, not a promotional adjective. | Rate from channel analytics in the condition where a web form improves, yet users still visit a branch because later evidence requirements remain unclear. | Vary the weight and test whether a need-based problem statement and journey map linking pain points to causes and owners remains preferred. |
| inclusion | Define it through the user problem across channels, not a promotional adjective. | Rate from abandonment logs in the condition where a web form improves, yet users still visit a branch because later evidence requirements remain unclear. | Vary the weight and test whether a need-based problem statement and journey map linking pain points to causes and owners remains preferred. |
| dependencies | Define it through the user problem across channels, not a promotional adjective. | Rate from journey maps in the condition where a web form improves, yet users still visit a branch because later evidence requirements remain unclear. | Vary the weight and test whether a need-based problem statement and journey map linking pain points to causes and owners remains preferred. |
| ownership clarity | Define it through the user problem across channels, not a promotional adjective. | Rate from accessibility needs in the condition where a web form improves, yet users still visit a branch because later evidence requirements remain unclear. | Vary the weight and test whether a need-based problem statement and journey map linking pain points to causes and owners remains preferred. |
| measurability | Define it through the user problem across channels, not a promotional adjective. | Rate from exception records in the condition where a web form improves, yet users still visit a branch because later evidence requirements remain unclear. | Vary the weight and test whether a need-based problem statement and journey map linking pain points to causes and owners remains preferred. |
| transition impact | Define it through the user problem across channels, not a promotional adjective. | Rate from stakeholder observations in the condition where a web form improves, yet users still visit a branch because later evidence requirements remain unclear. | Vary the weight and test whether a need-based problem statement and journey map linking pain points to causes and owners remains preferred. |
| Stage | Specific work | Owner | Decision receipt |
|---|---|---|---|
| Fix the question | Link the user problem across channels to an owner and end-to-end task completion rather than screen completion alone. | Engagement owner | Scope that can accept or reject a need-based problem statement and journey map linking pain points to causes and owners |
| Test the cause | Compare user research and channel analytics using abandonment logs. | Discovery lead | One explanation strengthened and another weakened |
| Option gate | Compare polishing the interface and automating the form on task completion and burden. | Sponsor | Continue, change, or stop |
| Bounded wave | Implement a need-based problem statement and journey map linking pain points to causes and owners with rollback and a benefit owner. | Outcome owner | Observable change in end-to-end task completion rather than screen completion alone |
| Review | Separate the effect where a web form improves, yet users still visit a branch because later evidence requirements remain unclear from demand or mix change. | Benefit owner | Benefit with attribution limits |
| Handoff | Transfer the definition of end-to-end task completion rather than screen completion alone and the the user problem across channels decision record. | Service owner | Local ability to repeat measurement |
Boundary for the user problem across channels: escalate specialist legal, security, or financial questions and keep their effect visible in a need-based problem statement and journey map linking pain points to causes and owners.
Lesson summary
The lesson links the user problem across channels to evidence, trade-off, execution, and measurement while exposing assumptions and limits.