Real problems. Working solutions.
Not finished case studies. Working answers being built and tested.
Each one exists because the available answer was too complicated, too passive or aimed at the wrong result. Status is stated as it is: building, testing, or waiting on the next proof. Nothing here claims a validated result yet.
The data existed. The useful signal did not.
Next proof Can it detect a meaningful deviation without false reassurance or false alarm?
Working model
* Boundary: never diagnosis.
The game gave the player more information than a player could use.
Next proof Can it improve the next decision without interrupting play?
Working model
* Boundary: recommend, never automate.
The website looked wrong. The business proposition was unclear.
Next proof Is the diagnosis consistently better than a generic automated audit?
Working model
Also on the bench
- P-04AddyssBuilding
The ad platform optimised the campaign. The business target came second.
Paid-media tools open with budgets and keywords, so the business number gets fitted around the media plan. Addyss starts at the target and calculates feasibility and budget backwards.
Current build — Backwards planning model in progress.
Next proof Can backwards planning produce a budget useful enough to guide a real campaign?
Working model
Business targetFeasibility + budgetDeviation → decision - P-05Hoshin BuilderNext proof
The strategy existed. The links between priorities, owners and actions did not.
Strategy matrices produce a document while the relationships stay in someone's head. The builder guides the links between aim, priorities, actions, measures and owners.
Current build — Guided linking flow drafted; follow-through not yet observed.
Next proof Does it improve follow-through, or only produce a cleaner matrix?
Working model
AimPrioritiesActionsMeasures / owners