Friday Deep Dive
One focused day to unblock a stubborn problem.
I work best where the issue is logic, structure, or execution: messy reporting, brittle automation, unclear workflows, half-built internal tools, or product ideas that need a sharper operating shape.
The format
What this is
A focused engagement for defined problems that need progress, clarity, and working output — rather than endless discussion.
Not a discovery process. Not a proposal. One day, one problem, something useful at the end of it.
Representative scenario
What a typical engagement looks like
Problem
A catering operator with manual supplier reconciliation. Three people spending six hours a week cross-checking invoices against delivery notes, with regular disputes and no single source of truth.
Thursday
A thirty-minute call to align on the exact problem scope, what a useful Friday output would look like, and what data or access is needed. Nothing ambiguous going into Friday.
Friday
A focused work block — typically four to six hours — building a working reconciliation tool with clear matching logic, an exception flag system, and a short ops note.
Handover
A structured end-of-day handover: the working tool, a brief explanation of the logic, and clear guidance on what to do next. No open loops.
This is a representative scenario, not a documented case study. It illustrates the scope and working style.
Fixed-price engagement
Commercials based on engagement.
One problem. One focused day. One clear handover.
Thursday alignment
Focused Friday work block
End-of-day handover
I run one Friday Deep Dive at a time to keep the work focused.
Problems
Where it tends to work best
- Reporting or BI workflow bottlenecks — dashboards that drift, KPIs no one trusts, definitions that never quite settled
- Fragile operational processes — manual work, unclear ownership, steps that rely on the right person knowing the right thing
- Automation opportunities — where the groundwork is done but no one has had a day to make it actually work
- Internal tools that need structure — half-built, hard to hand over, or built for a problem that has since moved
- Product or workflow decisions that need narrowing — ideas that need a clear operating shape before anyone commits to building
Process
How it works
Short alignment on Thursday
We define the success state clearly before the day begins — what the problem is, what a useful output looks like, and what is in scope. No ambiguity going into the work.
Focused build and decision-making on Friday
I work on the problem without interruption — analysis, structure, prototyping, or build, depending on what it needs. The time is used for the actual work, not for discovery or further scoping.
Clear handover at end of day
You receive a working output, structured notes, and a clear view of next steps. Not a proposal for more work — the thing itself, to whatever level the problem warrants.
Output
What you leave with
Output depends on scope. Typical outcomes include:
Working prototype
When the scope warrants build work, you leave with a working first version rather than a recommendation.
Structured analysis
If the right move is diagnostic, you get a clear analysis with priorities and decision implications.
Cleaned-up workflow
For process bottlenecks, the output can be a simpler, more workable flow with ownership and handover clarity.
Scoped decision document
Where build is premature, you receive a bounded decision document that makes next steps explicit.
Rebuilt or clarified operating logic
For reporting or tool problems, the output can be a cleaner logic layer that is easier to trust and maintain.
Fit
Good fit / not a fit
Good fit
- Clear bottleneck with a defined owner
- Real urgency — it needs to move
- Problem scope that fits one focused day
- Willingness to define success before the work starts
Not a fit
- Open-ended retainers or long-horizon delivery
- Generic IT support or admin-heavy operational work
- Undefined "help with anything" briefs
- Projects with no clear success state going in
Proof
How I work and what I build
The best signal on whether this is a good fit is seeing how I approach problems — not a client list.
Apply for a Friday Deep Dive
Share the bottleneck, why it matters now, and what useful Friday progress would look like.
FAQ
A few practical questions
How do I know if my problem is the right scope?
If you can describe the problem and a useful output in one paragraph, it is probably in scope. If you cannot, a short conversation first is the right move — that is fine and there is no commitment in asking.
What if the problem turns out to be bigger than expected?
The Thursday alignment is specifically there to catch this. If the scope is genuinely too large for one day, I will tell you that then — not on the Friday when the time is already allocated.
What kinds of output should I expect?
It depends on the problem. It might be a working prototype, a process map, a structured analysis, a rebuilt dashboard, a scoped spec, or a cleaned-up workflow. The output matches what the problem actually needs.
What does the Thursday alignment look like?
A short working session — usually 30 to 60 minutes — to confirm the problem, define what success looks like, agree on what is in scope, and make sure I have what I need to work without interruption on the Friday.
Is this ongoing work or a one-off?
It is designed as a single, bounded engagement. If the problem turns out to have a natural follow-on, that is a separate conversation after the first output is in your hands.