The Brief Template
A one-page format built to replace the three-paragraph Slack message that starts most requests.
A working program, not a lecture series
Write the brief that gets answered by Friday, not next quarter.
Hodalu Ditime trains operations and product managers to frame requests so clearly that data teams can actually act on them. Fewer back-and-forth threads. Fewer guesses about what you meant. More analyses that ship the same week they're asked for.
The Five Questions
What to answer yourself before an analyst ever sees your request.
The Turnaround Math
Why a well-scoped ask moves through a queue in hours, not weeks.
Common friction points
Where requests actually get stuck
Data teams rarely sit idle. What slows a request down is almost always visible before an analyst opens a single tool.
01
Ambiguous scope
A request that could reasonably answer three different questions, so the analyst has to guess which one you meant.
02
Missing context
No mention of what decision the numbers are supporting, which makes it hard to know what level of precision is even worth the time.
03
No decision attached
Data delivered with nowhere to go. Interesting, maybe, but nobody acts on it, so the next request gets deprioritized too.
04
Wrong format requested
Asking for a dashboard when a single number would answer the question, or asking for a number when a trend is what's actually needed.
Program overview
A curriculum built around real requests
Instead of general communication theory, each session works from requests your team has actually sent, or received. The goal isn't to make anyone sound smarter. It's to make the next request easier to act on.
- Framing the Ask. Turning a vague question into something an analyst can actually scope.
- Writing the Brief. Context, constraints, and the decision it supports, all on one page.
- Reading What Comes Back. Interpreting results without over-reading a small sample or under-reading a clear signal.
- Building the Habit. Templates and checkpoints your team keeps using after the sessions end.
Who this is for
Built for the people who file the requests
Operations Managers
Anyone who files recurring reporting or process requests and wants those requests to stop coming back with clarifying questions.
Product Managers
Managers scoping feature, pricing, or usage questions who need an analysis fast enough to still inform the decision at hand.
Program & Project Leads
Leads coordinating requests across multiple stakeholders, where one unclear brief can stall an entire cross-functional timeline.
Team Leads Routing Requests
Leads who submit questions on behalf of a wider group and need a shared format everyone on the team can use consistently.
How a session runs
The approach, in four steps
01
Diagnose
We look at how requests currently move through your team, from first Slack message to final answer, and note where they stall.
02
Practice
Participants rewrite real briefs during live sessions, not hypothetical case studies, and get direct feedback on scope and clarity.
03
Template
Everyone leaves with a one-page brief format built around their own team's language and typical request types.
04
Reinforce
A short follow-up session after the first few real requests go out, to adjust the template based on what actually happened.
Questions we hear often
Frequently asked questions
Mostly operations managers and product managers, along with program leads and team leads who route requests on behalf of a group. Some sessions also include a data or analytics lead so the framing gets tested from both sides.
No. The program focuses on framing requests and interpreting results, not on running analysis yourself. Familiarity with basic terms like sample size or trend versus average is helpful but not required going in.
Both formats exist. Individuals typically join a cohort workshop or the self-paced companion course. Teams that submit requests together usually get more from a team intensive, since the templates get built around their shared language.
General communication training rarely addresses the specific shape of a data request: scope, decision context, timeline, and format. This program works exclusively with that structure and with examples pulled from real request threads.
No. The program is about how requests are framed before they reach an analyst or a data team. It complements the work of an analytics function rather than replacing it.
Cohort workshops, half-day team intensives, a self-paced companion course, and short refresher sessions for teams that have already been through the program once. Details are on the What We Offer page.