Research quality
Brief quality as compound interest
A bad brief taxes everyone downstream: PMs trade on stale headlines, risk chases ghosts, and compliance inherits ambiguous sourcing. A good brief is engineered: explicit ordering, time semantics on every non-obvious claim, one accountable editor per cycle, and diffs that show what changed since yesterday. Compounding arrives when juniors learn that ‘tight’ means respect for reader attention, not shorter word counts.
The tax of narrative sprawl
Unbounded briefs become wallpaper. Caps force prioritization: if everything is critical, resilience training atrophies.
Ordering economics: readers skim top-down under clock pressure. Place the two decisions today’s tape could force above analytical backfill.
A useful cap pattern: five macro, five micro, three event risks, two liquidity or funding notes—adjust to mandate, publish the schema.
Structure that scales
Macro, credit, equities, events—pick lanes that match your mandate. Cross-links to desk objects beat pasted paragraphs from twelve chats.
Stable section ids help machine diffs and push notifications—‘section moved’ should not break subscriptions weekly.
Editor rotation
Rotate the pen weekly with overlap day for handoff. Document style guide in ten bullets, not fifty.
Outgoing editor owes a ‘known sharp edges’ note: which names are disputed, which data is flaky, which PMs need a call not a bullet.
Sourcing rules
Every non-obvious claim gets a link or citation id. ‘Sources tell us’ without a handle is gossip, not research.
If you cannot source it before the bell, mark it explicitly as hypothesis—surprise in Q&A is expensive.
Conflict and dissent
Surface disagreements as alternate scenarios with owners—burying dissent guarantees blown-up meetings later.
Name the observable that would resolve the fork (‘if CPI core prints above X, retire scenario A’). Foggy forks re-litigate forever.
Metrics
Time-to-read, skip rate by section, and post-brief question volume in chat—if questions explode, the brief failed clarity.
Track ‘brief-driven trades’ qualitatively once a week; if nobody cites it, you are producing homework, not edge.
Client-facing extracts
Never forward internal brief wholesale; extract with provenance and legal review where MNPI touches.
Template extracts with checklist: stripped handles, revised timestamps, disclaimer block, replay links only where appropriate.
Retirement rituals
Kill recurring sections that nobody opened for thirty days—ceremonial content trains cynicism.
Quarterly ‘section obituary’: retire one heading with data on why it died—celebrates editorial courage.
Public desk routes referenced above
Same URL discipline applies after you authenticate—bookmarkable paths, no tenant data on these pages.
- Operating rhythm Template language for stages, owners, and completion rules in a mandatory morning loop.
- Product atlas Route-level map so reviewers can open the exact module that produced a figure.
- Guides Pair public guides with internal SOPs so training points at one narrative spine.
- Guided product tour Orient sponsors and new analysts on module boundaries before you encode them in a mandatory loop.
- Service status Public narrative around uptime; align its claims with what engineering will defend in postmortems.
Operator toolkits
Checklists and scripts you can lift into runbooks, vendor RFPs, or board appendices.
Editorial operations perspective; adapt to your information barrier rules.