Do you work on projects where decisions are already made?

No. I do not validate or decorate decisions that are already made for political, vendor or budgetary reasons.

Will you compromise architecture for speed or convenience?

No. I do not trade architectural integrity for delivery pressure or short-term optics.

Can you stay if leadership ignores architectural risk?

No. If high-risk decisions are knowingly taken against professional judgment, I disengage from the project.

Do you work without clear authority?

No. Architecture responsibility requires real authority. Symbolic roles without decision power are not effective.

Are you suitable for experimental or low-risk projects?

Usually no. My work is most effective in regulated, mission-critical or high-risk environments.

When Not to Work With Me

Architecture is a responsibility, not a service. There are situations where working together would create unnecessary risk, false confidence or architectural debt.

This page exists to save time - yours and mine - and to prevent engagements where accountability cannot be established.

Decision ownership Architectural integrity Responsibility first

Emil Slavin Enterprise Architect · AI Strategist Founder, SLAtech LTD (est. 2004)

We Are Not a Fit If

You are looking for approval of decisions that are already made
Architecture authority is symbolic and responsibility is unclear
Vendor or political pressure overrides risk and governance
Speed and optics matter more than long-term system behavior
Failure consequences are minimized or treated as hypothetical

Why These Boundaries Exist

Architecture decisions shape how systems fail, how organizations respond and who is accountable when problems surface. Pretending otherwise creates fragile systems and personal risk for the people signing off on them.

I do not participate in engagements that shift responsibility without authority or that knowingly accept architectural risk without transparency.

When Working Together Makes Sense

You are accountable for system outcomes, not just delivery
Architecture decisions must survive audits and incidents
You want risks stated clearly before irreversible decisions
You expect architecture to last years, not quarters

Responsibility Comes Before Architecture

If this perspective aligns with how you want decisions made, we can start with a focused architecture-level conversation.

Start Architecture Conversation