I run six teams at Warp. Not one of them is engineering. All of them run like engineering teams.
Marketing, benefits, people, talent, partnerships, ops. All six on
@linear, all six in
@claudeai Code.
I was a mechanical engineer at Apple, a software engineer at Facebook, then a PM at Google. The most useful thing I took out of all three was watching how those engineering teams worked. Five things they all did:
1/ Everything is written down. Every task has an owner and a state and anyone can go look at it. That sounds like bureaucracy but it does the opposite. Writing work down is what lets ten people work in parallel without a layer of humans in the middle asking each other for updates.
2/ Doing the same thing by hand three times is a bug. An engineer hits the third repetition and writes a script. In ops you can hit the three hundredth and still call it your job.
3/ Deadlines come from breaking the work apart into timed pieces. You cannot put a real date on something you have not decomposed, and the decomposition is the estimate. Every optimistic timeline I have ever been handed was someone skipping that step and hoping.
4/ You ask for the outcome and stay out of the method. People stop coming for permission once the request is clear enough that there is nothing left to ask.
5/ When something breaks, the conversation is about the system that let it break. In engineering that is called a post-mortem.
Because of these 5 things, I have changed how my teams operate.
Every week, I run a standup with each team around their Linear board. What happened last week, what we are focused on this week, feedback to each other, what is coming. Every engineering org runs this. But almost no operating team does.
The usual answer for a high-volume team is to hire an ops person to track the work.
I think my people should just be their own project manager. They have ten times the context on what actually matters this week. You lose an entire layer of admin and the prioritization gets better, not worse.
None of this would have worked three years ago. The tooling was not there. Now the person who needs the thing can just build the thing, and the work lands in Linear from whoever did it rather than from someone tracking them.
The surprise was how fast my team started getting addicted to Linear. Not because they love adding process, but because for most of them this was the first time their work was visible to everyone else.
Most operating problems are engineering problems that nobody bothered to engineer.