The reflex
The technical team runs like an internal supplier. The business decides what it wants, tech estimates and builds.
The real decisions are made elsewhere and arrive as tickets.
The builder’s reflex
“Our architecture is already deciding part of the roadmap. Let’s look at what it allows before we choose.”
Why
Build choices shape which offers are possible, how long they take, and what they cost. In a software product, the way prices are handled can make new pricing easy or awkward. In a service, capacity or equipment availability plays a comparable role. A team wants to offer regional pricing. The system handles a single price today. Before promising a date, someone has to examine the changes needed and the narrower solutions that might do.
That information serves as much to discover a possibility as to identify a constraint. An existing capability can make an option affordable when the group thought it was out of reach. Conversely, an apparently small change can push work onto support or accounting.
The skills complete each other. Delivery informs feasibility, sales informs commitments and demand, finance informs costs, operations informs continuity of service. No one craft holds the strategy alone, and a taste for technology says nothing on its own about a person’s commercial judgement.
The right depth depends on the decision. There is no need to turn every exchange into a detailed review. Present the options, the assumptions and the unknowns that change the call. An estimate stays an estimate; it has to be revisable when information arrives.
Try this
For an upcoming decision, prepare one constraint and one option, with the people who know the build:
“This option means changing … A narrower version would allow … We still need to check …”
Ask through which channel that information can arrive before the commitment. With no access to the meeting, send a note to whoever runs it. On a first project, compare two ways of delivering the same service.
After the call, check which assumptions guided the choice and when they will be re-examined. Do not promise a deadline or a budget on another team’s behalf.
From where you sit
- Engineering: lay out a possibility as much as a constraint, with its unknowns.
- Sales: hold the promise against the capacity available before committing to it.
- Finance: separate the initial cost from the cost of running it over time.
- Operations: show what each option changes in the daily service.
To discuss
Which capability or constraint should enter our next decision before we commit?