Now do the work.
"Understand what our operations reduce to and how we know they are working."
Why this exists
Handbooks accumulate. People read them once and cite them in arguments. We care about whether this handbook changes how you work, not whether you can recite it.
Operational Flow
Start clearly: Send kickoff documents before the call and confirm scope before work begins.
Communicate directly: Use one channel and assign one owner. Keep decision ownership obvious.
Estimate honestly: Break down tasks, state your confidence, label the buffer, and hold the line.
Reflect usefully: Assign one owner per action item. Follow up, close the loop, or explicitly abandon it.
Use the tools: Use our standard stack consistently, or propose a change through the proper channel.
What good looks like
- A new project starts and nobody asks how we do things. They just start.
- A client says the team felt unusually well-organized without knowing why. That is the handbook working.
- An engineer updates the handbook after a retro produces a process improvement. The files reflect how the team actually works today.
What NOT to do
- Don't quote the handbook to win an argument. If you cite process to shield yourself, you have lost the conversation.
- Don't treat these entries as complete. They represent our current understanding. Improve them.
- Don't hide behind process when judgment is needed. The handbook covers common cases, but you must handle the rest.
There is a version of this handbook that a team reads once and only returns to when something breaks. They look for the rule that should have prevented the disaster. That team missed the point. The point is for these rules to become invisible, absorbed into how the team moves, rather than kept in a drawer for emergencies. By the time a process entry works, you stop thinking of it as a rule. It is just what a project looks like at Kryft.
The operations handbook cannot fix bad work. It is just a head start on good work. The rest requires judgment, honesty, and the willingness to say uncomfortable things before they cost two weeks and a client relationship. You cannot write that into a document. You either bring it or you don’t.