Joas Haster

Understanding organisations.
Designing workable change.

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.

Joas Haster

Where I contribute

From the question to a workable next step.

A useful solution begins with understanding what needs to change, who it affects, and which choices make progress possible.

Understand the organisation

Bring the purpose, people and constraints into view. Trace a recurring problem back to the decisions, responsibilities and information behind it.

Make choices understandable

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.

Connect decisions to practice

Carry the reasoning into processes, access and technology. Make ownership explicit and check whether the result helps people do their work.

Sagacitas Architecture Decision Workbench

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.

Lite €0

One decision template, a worked Azure landing-zone example and a quick-start guide.

Get Lite

Core €49

For one practitioner. Includes reusable templates, a decision register, review dashboards and scripts to start a new record.

Buy Core

Pro & Team €99

For 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 & Team

One-time downloads through Polar. Terms of sale & refunds · Privacy

About Joas

A background in history.
A grounding in IT.

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

A closer look at the reasoning.

All notes

Decisions and governance English

A rejected option is part of the decision

Keeping the reasoning behind a rejection makes a decision easier to explain—and easier to revisit when its assumptions change.

Start a conversation

Does this sound like the way you work?

I’d be glad to talk about a role, an organisational question, or a possible collaboration.

joas@sagacitas.eu