Written-Expectation Operating System
Document the work before holding people accountable for it
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 99%
Wilner's operating model begins by putting expectations and processes in writing. A verbal instruction can be missed, misunderstood, or forgotten, which makes later accountability unfair and execution inconsistent. Written standards give a team member something to revisit, provide new hires with a substantial starting point, and let leaders specify how an intangible service should be delivered. The mechanism connects documentation to reputation: define the work, train against the definition, and then hold people accountable for producing the intended customer experience. Wilner also places this work before aggressive growth. Technology, compliance, and documented operations create the foundation that can absorb more business without service collapsing. As the organization reaches a new level, the standards and infrastructure must be rebuilt for the next scale.
Origin
Wilner recalls arriving at UWM when little was in writing and challenging supposed underwriting rules by asking leaders to show her the documented guideline.
Core principles
- 01Accountability requires a written standard
- 02Processes should define the experience the customer receives
- 03Documentation preserves knowledge when people miss a conversation
- 04A scalable foundation must precede rapid growth
How to run it
- 1
Identify reputation-critical work
Map the recurring tasks that directly affect the product or customer experience. Start where variation creates the greatest operational or compliance risk.
Pro tip Follow one real customer journey to find undocumented handoffs.
Watch out Do not try to document every minor activity before the critical work.
- 2
Write the standard
Describe exactly how the work should be executed and what acceptable completion looks like. Make the document usable without relying on the author being present.
Pro tip Ask a team member to point out phrases that permit multiple interpretations.
Watch out A remembered former rule is not a current written standard.
- 3
Teach from the document
Give new and existing team members the reference, then add training for the remaining context and judgment. Ensure someone who missed a live explanation can still recover the expectation.
Pro tip Use the document as the starting point rather than as an archive.
Watch out Documentation alone does not replace instruction or practice.
- 4
Create fair accountability
Compare execution with the written expectation and coach or correct against the same source. Exclude ethical and moral concerns, which do not require a written rule before action.
Pro tip Ask whether the standard was accessible and understood before judging a miss.
Watch out Do not punish people for an expectation that existed only in a leader's head.
- 5
Rebuild for the next scale
Review which processes and systems have stopped working at the current size. Return to foundational work before adding the next layer of volume.
Pro tip Treat scale thresholds as prompts to revisit the operating system.
Watch out What supported one stage of growth may fail at the next.
In the wild
When Wilner joined UWM, leaders sometimes called an issue a guideline because it had once been treated that way. She asked them to show where the current guideline was written, exposing how much operations depended on hearsay. UWM then spent substantial time writing processes and strengthening technology and compliance.
→ Team members gained clearer expectations and the company built a foundation capable of supporting growth.
Common mistakes
Managing by hearsay
An unwritten expectation changes as it passes between people and leaves no fair basis for accountability.
Scaling before the foundation
Bringing in more business before processes, technology, and compliance are ready can destroy service quality.
Is it for you?
Best for
It is best for service businesses adding people or volume faster than informal knowledge can travel.
Not ideal for
It is not ideal for novel work where no repeatable process or expected outcome yet exists.
From the transcript
“if it's not in writing for a team member to do X or Y, like it's very hard for me to hold them accountable to…”
“spend time like write down your processes. Write down and be thoughtful with it, so you know exactly how you want your team to execute…”
“you really got to lay the foundation to be able to grow”
From the episode
The Most Powerful Woman in Mortgage Melinda Wilner