Isolate citation-service release lead-time bottlenecks
Delivery friction often appears as a single delay even when its causes are distributed.
A visible queue can invite action before the team agrees on what the queue is actually signaling.
“We keep hearing an improvement is close, then it slips into the next release train.”
Woojin Tang · Knowledge Management Counsel
Depends on frequent, reliable workflow improvements for firmwide research and drafting standards.
What pulls against what
- visible delay vs. actual bottleneck
- qualitative friction vs. sampled telemetry
- automation breadth vs. targeted learning
- security intent vs. implementation overhead
What is at stake
Delivery has slowed, but the dominant cause is disputed. A focused experiment can prevent the team from automating the wrong bottleneck
Why Harvey
For Harvey, the pace of dependable improvements often affects how quickly legal workflows can respond to changing work.
Written for
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.