Aligning engineering with strategy: negotiated, not announced
Your teams know things the strategy needs. The common problem: there is no route for that knowledge to reach the decision while the decision is still open, so alignment gets attempted afterwards as communication. This page covers how Aurora Coach opens that route, and ends with the questions and the response record, free.
Alignment is not a communication problem
The instinct when a strategy is not landing is to communicate it again. Another all-hands, a clearer deck, a written memo. Teams then repeat the strategy accurately and keep working much as before, which gets read as the message still not having got through. It got through. Awareness was never the missing piece.
The missing piece sits earlier, in how the strategy was made. The people closest to the work hold information the decision needed: which bet is undeliverable on that timeline, which dependency nobody outside the team is tracking, what customers keep asking for, what the team could do that nobody upstairs knows is possible. Most planning cycles have no route for any of that to arrive while the decision is still open.
So a decision gets made with a missing input, and alignment gets attempted afterwards as communication. It cannot work, because you cannot explain your way into someone agreeing with a plan built without what they knew. Leadership still decides. They hold context the teams do not: runway, commitments already made, where the company is going next. But a decision improves when both sides put their information on the table first, and the agreement that comes out the other side is the alignment.
The common failure of the good version is consultation with no return path. Teams get asked, nothing visibly happens, and no one tells them why. That is worse than not asking, because it teaches a team that contributing is not worth the effort, and the next round of questions gets thinner answers.
None of this is new. In 1968 Melvin Conway observed that organizations design systems that mirror their own communication structures, which is a claim about software interfaces rather than about meeting invitations. The narrower point still holds and is worth stating plainly on its own terms: a communication path that does not exist produces nothing, and there is usually no path from what a team knows to the room where the quarter gets decided.
A team that helped shape the strategy does not need it explained.
How Aurora Coach addresses it
The target is a planning conversation that already contains what the teams know. This lives in Aurora Coach's Alignment domain, team enablement and strategic alignment, one of six domains of team effectiveness alongside Foundation, Product, Engineering, Operations, and Workflow. The loop that moves it has seven stages, and it starts by asking rather than telling.
- Sense + Analyze Context comes from the whole team, not the lead: the AI asks structured questions and each person answers in their own words. This is the channel most operating models are missing. What a team knows about a bet reaches the planning conversation as evidence rather than as a rumour someone repeats in a corridor. The AI synthesizes the collective picture into a strengths-and-gaps read grounded in the team’s actual situation.
- Recommend + Refine + Commit The AI recommends concrete next steps with rationale, implementation steps, and success criteria. Team members vote and the team lead refines to fit reality. The AI’s job is to inform the decision, not to make it. The commitment is the negotiated result, owned by the team because the team helped shape it, rather than a slide that gets re-presented next quarter.
- Execute + Re-evaluate The team works on it alongside delivery. The next period’s analysis shows whether the agreement held under pressure, which is the only test that matters: alignment is easy in a planning week and hard in week seven. Context compounds across periods, so each round of planning starts better informed than the last.
Because every team runs the same loop every period, the input arrives on a schedule rather than when someone remembers to ask, and it arrives per team rather than as an org-wide average that flattens the one team with the objection worth hearing. Free-text check-ins keep the route open between periods. If the gap is that nobody can say what the work was for, see output vs outcome. If people are not saying what they know, start with psychological safety, because none of this works on a team that does not feel able to disagree upward.
How do you align engineering teams with business goals?
By involving them while the goals are still being set, rather than explaining the goals better afterwards. The teams closest to the work hold information the strategy needs: which bets are undeliverable, which dependencies will bite, what customers keep asking for. Collect that before the planning cycle, decide with it in the room, and tell each team what happened to their input. Alignment is what is left over from that conversation.
Should engineering teams influence strategy, or just execute it?
Influence it. Leadership still decides, and should, because they hold context teams do not have: runway, commitments already made, where the company is going next. But a decision made without what the teams know is a decision made with a missing input. The useful model is negotiation between two informed parties, not consultation that collects opinions and files them.
What is strategic alignment in engineering?
The connective tissue between what a team executes and where the organization is going: shared objectives, cross-functional collaboration, developer experience, and the persistent work of removing impediments that are invisible from outside the team. In Aurora Coach it is one of six domains of team effectiveness. It runs in both directions, which is the part most implementations miss.
Six questions that surface what the teams know
Ask before the planning cycle, not after it. These only work if the answers can still change a decision; run them once the plan is set and you are collecting opinions, not input.
- What are we likely to be asked to do next quarter that you already know will not work? The load-bearing question. Teams usually know this months ahead and usually assume someone senior knows it too.
- Which dependency worries you that nobody outside this team is tracking? Cross-team dependencies are visible from inside a team and close to invisible from above. This is knowledge the planning conversation does not otherwise have.
- What keeps coming back from customers that never reaches a plan? Support patterns, sales objections, the same question in every onboarding call. Teams accumulate this and rarely have a route for it.
- What could this team do that leadership does not know is possible? Teams get asked about risk constantly and about capability almost never. Some of the best strategic options in a company are sitting unmentioned in an engineering team.
- Where are we spending effort you believe produces nothing? Naming it is a strategy input, not a complaint. Stopping something is a decision only leadership can authorise, so it needs to reach them.
- What would you need in order to commit to an ambitious version of this? Turns a flat no into a negotiation. The answer is usually specific and often cheaper than the alternative plan.
The response record
Six fields, one row per input. This is the half that turns asking into negotiating, and the half almost everyone skips.
- The input, in the team’s words Not summarised into management language. The wording is the evidence, and rewriting it is how the substance goes missing.
- Who raised it So the response goes back to a person rather than into a channel. Named inputs get answered; anonymous ones get filed.
- The decision: adopted, adapted, or declined All three are legitimate. Leadership still decides. What matters is that a decision was made and recorded rather than the input simply going quiet.
- The reasoning, especially when declined A team that hears "we considered it and chose otherwise, here is why" stays engaged. A team that hears nothing learns that contributing was not worth the effort.
- What changed in the plan Concrete, or explicitly nothing. This is the field that proves the exercise was real, and the one that is uncomfortable to leave empty twice in a row.
- Who takes the answer back One named person and a date. An input with no return path teaches the team not to bother next time, which is worse than never having asked.
Declining most of what comes back is a perfectly good outcome. Leadership sees things the teams cannot, and a strategy that adopts every input is not a strategy. What matters is that every input got an answer, because that is what makes the next round worth answering honestly.
Not ready to change anything today? You already have the questions and the response record above, copy buttons and all. If you want one improvement loop like these in your inbox each month, leave your email.
You have the questions and the response record above, yours to keep and to run without buying anything. It is also generic, as any page has to be. What it cannot tell you is which of it applies to your team, in your situation, this quarter. That judgement is the actual work.
That judgement is what Aurora Coach does. Your team supplies the context through Coaching Sessions and check-ins, in its own words, every period. The AI works from that context rather than from a template, and recommends specific next steps with the reasoning and how you will know whether it worked. The team decides and commits. The next period shows whether it held. This page is one problem in the Alignment domain. The loop runs across all six, with every team, every period.
What it costs to run: one Coaching Session per person per period, fifteen to twenty minutes, and a period defaults to four weeks with the team setting its own. What the team writes stays private to that person. Only the team-level picture rolls up to leadership.
Both are free. No signup, about two minutes.