Built for consultancies.
Overshow works from the screen context, documents and meeting transcripts each consultant allows. The examples below show what a consultancy keeps from each kind of work once the consultant shares it.
Management and strategy
Senior consultants spend the day in workshops, client calls and steering groups. The reasons behind a recommendation are the first thing forgotten, and the first thing a new partner on the account asks for.
- Client requests and commitments, with the source
- The recommendation, and the options ruled out
- Scope changes: what came in, what went out, who asked
- Commitments made to and by the client team
- Risks raised, and what the client agreed to do
Client asked for the Germany rollout in the June release.
Phased rollout chosen. The single-release option exceeded the budget.
Client team to confirm data residency by Friday.
The engagement
The engagement. Each day's notes add up to one dated history of the engagement.
Outcomes
Review scope changes before deciding what to invoice. Give the next partner a dated account of requests, decisions and what the client still has to agree.
Technology and delivery
Design decisions, trade-offs and incident lessons live in pull request threads, incident channels and pairing calls. Little of it reaches the repository, and less reaches the client's project managers.
- Design decisions and the options ruled out
- Trade-offs accepted on cost, performance, and security debt
- Incident lessons: root cause and follow-up actions
- Interface commitments made to other teams
- Things to revisit later, with the date they were raised
Event-driven sync chosen. Nightly batch would delay client updates.
Repeated retries caused the incident. Limit retries to 120 seconds.
Webhook schema v2 promised to the billing team by month end.
The engagement
The engagement. A decision history builds up that the next consultant on the account can read.
Outcomes
Keep the reasons behind a design decision available for handover. Use saved excerpts to prepare change reviews and explain what the team agreed.
Advisory and audit
Advisory and audit work runs on interviews, working papers and privileged conversations. The notebook records what was reviewed. The reasoning, the lines of enquiry dropped, and the client's verbal commitments usually go missing.
- Findings, with who said what and the source
- Lines of enquiry raised and dropped, with the reason
- Method changes mid-engagement, with the reason
- Open questions flagged for follow-up
- Client commitments: evidence promised, sign-offs given
Vendor access has no expiry date. The client will confirm who owns the account.
Legacy payroll work excluded from the review. More evidence is needed.
Evidence pack and board sign-off promised by 22 Apr.
The engagement
The engagement. Findings and their saved excerpts come together in one place for review.
Outcomes
Give a reviewer dated findings with the saved source excerpts. Keep open questions and their owners available when a partner hands work over.
See it on a walkthrough
A 30-minute walkthrough, or a paid set-up on one engagement.