Examine the system
Turn a confusing situation into a map you can point at.
By the end of this lesson
- Map who holds what, and where information stops moving
- Find services that duplicate each other and gaps nobody covers
- Locate the actual bottleneck rather than the visible symptom
Watch
Episode B02
The video for this lesson has not been produced yet. The narration below is the same script, and it plays now.
Transcript
Before solving a problem—make sure you understand the system creating it. Otherwise, you may only make the symptom more efficient.
The second step of the BEACON Framework is: Examine the System. Turn confusion into a map.
Ask: Who is involved? Where does information move? Where does it stop? Which services overlap? Which connections are missing? What policies, incentives, or distrust make progress harder?
AI can organize documents. Compare programs. Summarize policies. Map stakeholders. Identify repeated patterns. And help us see relationships that were difficult to recognize when everything lived in separate places.
Without that map, we may build another program where three already exist—while missing the one connection people actually need.
Choose one community problem. Map five things: the people, the resources, the process, the barriers, and the missing links. Then ask where one small change could improve the entire flow.
Do not rush to create another solution. First discover why the current solutions are not connecting.
When intelligence reveals the system, action becomes more precise.
The lesson
This is the step where the technology earns its place most clearly, because the work is genuinely large and genuinely mechanical. Reading twenty pages of policy, four annual reports and a council agenda to work out who is responsible for what is exactly the sort of task that used to make people give up before starting.
What you are looking for is not a list of organisations. It is the shape of how something moves — or fails to. Where does a person enter this system, what happens at each step, and at which point do they most often stop? The stopping point is usually not where the complaints are; complaints cluster where people are still engaged enough to complain.
Two findings recur often enough to look for deliberately. Duplication: several bodies doing near-identical work without knowing about each other, which is common and rarely malicious. And gaps: a step everybody assumes somebody else covers, which is where most people actually fall out.
The output should be something you could put in front of someone who works in the system and have them correct it. That is the standard — not that it is complete, but that it is concrete enough to be wrong in a specific way.
Straight from the framework
E — step 2 of 6
Examine the system
What are the institutions, resources, barriers, and information flows?
Turn confusion into a map. Note duplicated services and missing ones.
Do this in the app
Put the lesson down somewhere real
Answer the second worksheet field with what you have mapped: who holds what, and where things stop.
Done when — Two of six steps are answered.
/dashboardUse the review button on that answer and read what comes back before accepting anything.
Done when — You have a score and a note, and you decided for yourself what to keep.
/dashboard
Go further
Check yourself