Understand the organisation
Bring the purpose, people and constraints into view. Trace a recurring problem back to the decisions, responsibilities and information behind it.
Sagacitas
Joas Haster
I connect organisational questions with the architecture and technology needed to make change work.
Open to roles in enterprise architecture, information advisory and digital transformation.
Where I contribute
A useful solution begins with understanding what needs to change, who it affects, and which choices make progress possible.
Bring the purpose, people and constraints into view. Trace a recurring problem back to the decisions, responsibilities and information behind it.
Turn competing needs into clear requirements and explain the consequences of each option. Give people enough context to make a decision they can stand behind.
Carry the reasoning into processes, access and technology. Make ownership explicit and check whether the result helps people do their work.
Who owns this decision now? And what would make us reconsider the option we turned down?
Use these software engineering and IT documentation templates to keep Architecture Decision Records for Enterprise Architecture work. Give each decision an owner, record why an option was rejected, and specify what evidence would bring it back for review.
Markdown and Git work out of the box. In Core and Pro, enable Dataview in Obsidian to use the live dashboards.
One decision template, a worked Azure landing-zone example and a quick-start guide.
Get LiteFor one practitioner. Includes reusable templates, a decision register, review dashboards and scripts to start a new record.
Buy CoreFor a team or consulting practice. Adds five worked enterprise decisions, trade-off and sign-off tools, an automatic index and GitHub Actions checks.
Buy Pro & TeamOne-time downloads through Polar. Terms of sale & refunds · Privacy
About Joas
My background combines history with hands-on IT. That makes context an important part of how I approach a question: how did we arrive here, which assumptions still hold, and what would make a different choice possible?
My focus is the relationship between organisations, information and technology. I enjoy making that relationship understandable—in a clear requirement, a considered decision, or a system people can actually work with.
The notes here explore those connections through small, concrete examples.
Notes
Authority, secrecy and competing commitments in Harry Potter
Keeping the reasoning behind a rejection makes a decision easier to explain—and easier to revisit when its assumptions change.
Start a conversation
I’d be glad to talk about a role, an organisational question, or a possible collaboration.
joas@sagacitas.eu