Problem Analysis
idea
Date:
2015-10-01
Tags:
notes
analysis
map the phases:
customer actions (user) frontstage action (ui) backstage actions (backend) support processes (manual)
how to research the issue
interest
build measure learn
- What are needs?
- What are requirements?
- What are obstacles, static, unmoveables?
- What is out of scope?
Where are leverage points?
scope the problem
identify desired solution
identify current state
work backward from solution (what does it look like looking backward from the finish line?)
- user wants to answer a question
- user wants to see if this has been solved before
- user needs to find data to answer it
- user goes to data catalog to browse datasets
- user goes to data catalog to search for datasets
- if yes - fork the solution
- update the solution
- if no - reach out for help
- if no help - slug through it
- meet with users
conduct analysis
- look for existing policy
- look for existing legislation
write a report
- look for an existing template
- if none
- write a new report
- if yes
- use the template
- complete the template
presenting and communicating the Results
- next steps
By Ryan Wold · © 2015–2026 Ryan Wold
Licensed CC BY-NC 4.0. AI training requires a license — machine-readable terms.
Tip: $afomi on HandCash · afomi@handcash.io