Influence Without Authority
Getting decisions adopted when you cannot mandate them.
6 to work through
-
advanced Multiple choice
A written standard says every new service must emit structured logs with eight required fields. Twenty-six teams ship roughly 30 new services a year and about 45% comply. Which change most reduces the annual cost of this standard?
3 min answer -
advanced
After a full review the CTO chooses an approach you argued against. You believe it will cause serious problems in eighteen months. What do you do?
2 min answer -
advanced
An architect has no authority over the teams whose systems they are responsible for. What actually produces influence, and what destroys it?
2 min answer -
advanced
An architect must change how several teams build without the authority to direct them. What works?
2 min answer -
advanced
An architect must get several teams to adopt a shared approach and has no authority over any of them. What actually works?
2 min answer -
advanced
How would you change the technical direction of a team that does not report to you and disagrees with you?
2 min answer
3 terms in this topic
Credibility Budget
The finite standing an architect has to override or refuse, earned by being useful and by being right about things that mattered - and spent delibera…
practiceInfluence Without Authority
Getting decisions made and adopted by people who do not report to you — which is most of the architect's job.
conceptUnenforced Standard
A written rule with no mechanism behind it - an anti-pattern whose cost is paid per decision in argument and divergence work while compliance stays p…
Neighbouring topics
Meta-Skills
General material on how architects think and work.
Systems Thinking
Interactions and feedback loops rather than isolated components.
Trade-off Analysis
Making costs explicit and comparable rather than asserting a preference.
First-Principles Reasoning
Reducing to physics, mathematics and economics, then reasoning up.
Failure Thinking
Asking of every box and arrow how it fails and how you would know.
Constraint Thinking
Designing for the budget, skills and regulations that actually exist.
Pattern Recognition
Seeing a familiar problem, and checking whether the forces match.
Pragmatism
The simplest architecture that meets the requirements usually wins.
Judgement Under Uncertainty
Choosing the best worst case when information is missing.
Business Understanding
Connecting a design to the outcome that pays for it.
Mentoring
Growing architectural judgement in other people.
Continuous Learning
Staying current without chasing every new thing.
Estimation
Sizing work and cost honestly, with the uncertainty stated.
Prioritisation
Choosing what not to do, and defending it.
Research & Evaluation
Assessing a technology quickly without adopting it by accident.
Handling Ambiguity
Making progress when the requirements are not yet knowable.
Technical Leadership
Setting direction and carrying accountability without a team reporting to you.
Ethics in Architecture
Privacy, accessibility, sustainability and the consequences of a design.
Career Development
Growing from senior engineer to architect and beyond.