People, Product and Process
On her first Monday as a manager, Meera opens her laptop and reaches for the payment-retry bug she was fixing last week. By noon three messages have landed: Neha has been stuck for two days and was scared to ask, Rohan wants a launch date for UPI autopay, and the deploy took forty minutes again. None of them is a coding problem, and all of them are now hers.
The rule
Your output is now your team's output: its people, product and process.
Until last month Meera was a senior engineer on the checkout team at Haat, an online grocery app. Now she manages it: Farhan, the tech lead, plus Priya, Arjun, Kabir and Neha. Her work falls into three areas.
| Area | The question it answers | Meera's Monday |
|---|---|---|
| People | Can everyone do their best work, and are they growing? | Neha stuck and afraid to ask |
| Product | Are we building the right thing, and building it well? | Rohan needs a realistic date |
| Process | Does work flow smoothly from idea to customer? | A 40-minute deploy |
- People covers hiring, one-on-ones, feedback, career growth and keeping the team healthy.
- Product means working with the product manager, Rohan, on what to build and why, and owning the quality, reliability and technical health of what ships. Rohan decides priorities; Meera makes sure the team can deliver them without cutting corners it will regret.
- Process is how the team plans, reviews code, releases and handles incidents: enough structure to be predictable, never so much that it slows people down.
What changes most is how you are measured. As an engineer, Meera was judged on what she built. As a manager, she is judged on what five people build, how well they work together, and whether they are better engineers a year from now. An hour spent unblocking Neha can be worth more than a day of Meera's own code.
The shortcut
When something lands on your desk, sort it into people, product or process, then ask: "What would let the team handle this without me next time?" The first question tells you what kind of problem it is. The second turns a one-off fix into a lasting one.
Neha is stuck → people
The real problem is not the bug; it is that asking for help feels unsafe. Meera pairs her with Priya today and sets a team norm: stuck for an hour, ask in the team channel.
The trap is treating coding as the "real work" and everything else as interruptions. For a manager, those interruptions are the job.
Drills
Answer fast — trust the rule.
Engineers wait forty minutes for every deploy. Which area does this belong to?
Meera's team ships UPI autopay on time, but two engineers are now quietly job-hunting because of how the push was run. How is Meera doing?
Rohan asks whether "save card for later" or "split payment" should come first. What is Meera's part?
Which is the best measure of how well an engineering manager is doing?
Remember
- Your output is now your team's output: its people, product and process.
- Sort each problem into one of the three, then ask what would let the team handle it without you next time.
- The trap: treating code as the real work and management as interruptions.