Intel / Brief / Monday Intel

Monday Intel N°7: Ask what you can decide.

Ownership is easy to promise and harder to define. Before accepting a consequential role, find out which decisions are yours, which need agreement and what support exists.

NXT Eng4 min read

You will own this is an attractive sentence in an interview. It can mean authority over a real problem. It can also mean being accountable for an outcome while someone else controls the roadmap, budget and technical choices. Before you compare titles, ask what ownership lets you decide.

Turn the promise into a recent example

Ask the team to describe a real decision the person in this seat would have made recently. It could be delaying a release, replacing a vendor, narrowing a feature or choosing which reliability issue gets fixed first. Who made the call? Who had to agree? What happened when someone objected? A specific example is more useful than another statement about an entrepreneurial culture.

If the role is new, make the question hypothetical and label it that way. Walk through a plausible tradeoff together. The point is not to demand a settled organization chart from an early team. It is to discover whether you share an understanding of how decisions will work.

Separate three kinds of ownership

  • Execution: you choose how to deliver work within a direction someone else sets.
  • Technical direction: you shape architecture, quality standards and technical tradeoffs, with clear boundaries around product or commercial decisions.
  • Outcome: you help define the problem, choose the approach and change priorities when the evidence changes.

None of these is inherently the best arrangement. An excellent specialist role can offer deep technical direction without owning the business outcome. The problem is a mismatch between the authority you expect and the authority the team intends to give you.

Find the boundaries before you find the conflict

Ask what you can decide independently, what needs consultation and what needs explicit approval. Then ask where you go when two priorities collide. A founder may need final say over spending or a customer commitment. A security review may limit a technical shortcut. Boundaries are not automatically a warning sign. Unstated boundaries are much harder to work with.

For founders, this is part of scoping the seat. If you want a hire to own reliability but will not let them change the release plan, say how the conflict gets resolved. If the person must improve a system without another hire or a larger budget, make those constraints visible before the offer.

Authority still needs support

Decision rights do not substitute for access, context or help. Ask who owns adjacent systems, which resources are committed and who will unblock a dependency. Being the first engineer in a function is different from being the only person allowed to care about it. A credible answer should explain the working relationship, not just praise your ability to figure things out.

Ownership is not how many problems land on your desk. It is the connection between your responsibility, your authority and your support.

This week’s move

Before your next offer conversation, write a short decision map: what I own, what we decide together and what I escalate. Ask the hiring manager to correct it. The corrections may tell you more about the seat than the title. For founders, do the same exercise before opening the search. Clear authority makes a consequential role easier to explain and more honest to accept.

Open a private conversation.