Operations
Case study: Consolidating research after a spin
Anonymous composite: a lean team inherits overlapping feeds, duplicate screeners, and a wiki decayed into noise. They must converge morning workflow without pausing coverage, trading political capital for a narrow intervention: freeze new tools, one brief index, calculator links in external email, and measurable dispute migration.
Baseline operating picture
Three paid feeds with partial overlap, two screeners maintaining separate watchlists of the same symbols, a Confluence nobody searched, and a drive structure that rewarded loudest-in-chat naming.
Morning ritual averaged forty minutes before the first original thought; most time went to reconciling ‘what changed’ across silos.
Political constraint: no hiring window; no big-bang vendor swap; leadership explicitly nervous about morale.
Intervention design
CIO messaging: ‘we pause net-new tooling to stop bleeding minutes’—paired with visible removal of two zombie pilots nobody used.
Single brief index owned by rotating editor; drill queue capped WIP to avoid infinite homework lists.
External email rule: any figure with a desk calculator counterpart must carry the link, not a PNG—exceptions require named VP approval to create friction intentionally.
Week-by-week signals
Week 1: ticket volume spikes as UX traps surface—good; means people attempted the spine.
Week 2: first wins—two PM arguments resolved via parameter toggles same day.
Week 3: holdout pockets in legacy email—targeted 1:1s, not mass scolding.
Week 4: median prep time down double digits; subjective stress scores improved in post-month poll.
Measurement rigor (lightweight)
Counted ‘duplicate stress questions’ in macro channel before/after; dropped materially.
Tagged IC packs with ‘has runnable link’ boolean; share climbed from 18% to 76% in six weeks.
No claims about alpha; coordination metrics were the success story Finance believed.
Tracked ‘time to first disagree-on-parameter-not-person’ as an informal PM sentiment metric—lagged volume by a week but predicted retention.
Friction inventory encountered
Legacy compliance worried about client-visible links until legal language clarified the same controls as emailing spreadsheets—relationship risk lowered once counsel saw version pins.
One star PM insisted on PNG ‘for aesthetics’—allowed only outside quantitative footnotes; shrunk scope over time.
What we would do differently
Start the VP exception list empty; adding two names early created moral hazard.
Instrument time earlier; anecdote fights wasted a week that metrics would have settled.
Sixty-day and ninety-day echoes
At day 60 they removed provisional watermarks on legacy drives that confused search. At day 90 they revoked five dormant SaaS seats whose only traffic was password resets—budget owners noticed.
Second-order effect: recruits cited ‘adults in the room on tooling’ in exit interviews far above baseline—retention signal not in the original business case.
Stakeholder map (simplified)
CIO: capacity narrative and kill list for zombie pilots. Head of research: editor rotation for brief. PM leads: link mandate in external mail. Compliance: language parity with spreadsheet policy. BD: client comms on why links beat opaque attachments.
Playbook excerpt (email + huddle)
CIO email (week zero, verbatim tone): ‘We are pausing net-new research tools for thirty days—not because ideas are bad, but because our minutes are leaking to reconciliation. You will see two zombie pilots removed this week; that is the trade. The brief index is the spine; exceptions to the link-not-PNG rule require VP sign-off so we do not quietly relearn spreadsheets in email.’
First ten-minute huddle script: ‘State one duplicate stress you heard twice this week; we resolve it with parameters or a ticket, not a third meeting.’ Closer: ‘If a figure matters externally, paste the replay link in-thread before you leave the room.’
How to read this composite
Treat this narrative as an anonymized pattern library, not a promise that your shop can copy timings or percentages.
Steal the intervention shapes—freeze, index, link mandate—not the politics; regulators, unions, and data rights differ.
If one section matches your situation, run a two-week pilot on that slice before debating enterprise rollout.
Caveats and limits of narrative
Composite means deliberately anonymized timelines; do not benchmark your shop without adjusting for regulator, union, and data-rights realities.
No performance, alpha, or client-specific claims are implied—only operating mechanics.
Copy patterns, not numbers: your baseline times and adoption curves will differ.
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.
- Public calculator hub GET-shareable patterns you can mirror for every material desk run; use as the pattern for replay links.
- 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.
- Platform framing How tenancy and public chrome split when SEO and auth walls must coexist.
- Readiness JSON Coarse liveness contract—use it to rehearse what is safe to expose anonymously vs behind auth.
- Sitemap XML Canonical index of what you intend to be crawled—diff it when generators change.
Operator toolkits
Checklists and scripts you can lift into runbooks, vendor RFPs, or board appendices.
Composite only; not a customer reference; not a performance claim.