Live · Free
Map your data. Surface what is blocking. Walk away with a prep plan.
An extracted work session built off FridayOS. You bring a workflow that isn't moving because the data underneath it isn't ready; Friday helps you inventory the sources that workflow depends on, surface what's blocking, and produce a prep plan you can execute Monday. Best taken after Workflow Sprint — the workflow anchor sharpens the inventory — but it runs standalone too.
The arc
A short read on you, the business, and the workflow this data prep serves. If you did Workflow Sprint, the anchor pulls from there; if not, we name it here.
Surface every data source the anchor workflow depends on — systems, files, manual sheets, exports, external feeds. Location, owner, format, freshness for each.
For each source, against the workflow: clean, needs-prep, or blocked — and for every non-clean source, the specific blocker named from the seven-category library.
What you'll walk away with
The sources your workflow depends on, inventoried; what's blocking, surfaced; and a concrete plan to get the data ready. Yours to keep and execute.
Also from Framework Friday
Concrete prep actions, each with a named owner and an effort estimate, ordered by what unblocks the workflow first — not by what's easiest.
Your prep plan goes through the readiness rubric — 25/35/40 across Discovery, Documentation, and Execution, plus four must-haves. Returns Ready / Almost There / Needs More Depth.
Your data prep plan, your readiness summary, and the bridge into FridayOS — where the prep actions become tracked work.