1. Context
What kind of organization or situation is this? Keep employer, customer, product, and system names generic.
Free help
Bring one real business architecture problem.
No form, account, mailing list, or sales funnel. Send a focused question by email and I will give you a practical, best-effort response grounded in the decision you are trying to improve.
Email support
Make the question answerable.
The best messages are short enough to understand and specific enough to act on. Use the structure below; delete anything that does not matter.
2. Decision
What decision, alignment, diagnosis, model, study goal, or career choice are you trying to make?
3. What you tried
Describe the artifact, approach, or distinction that is not working. A sanitized excerpt is fine.
4. Constraint
What makes the obvious answer impractical—time, authority, data, sponsorship, governance, tooling, or organizational politics?
Good uses
What I can help you work through.
The emphasis is applied judgment: choosing, structuring, linking, and using architecture—not merely defining it.
Capability and value-stream critique
Leveling, naming, definitions, scope, stakeholder perspective, stage logic, and the point where architecture has turned into process or organization design.
Choosing the right BA package
Translate a vague request into a decision-centered engagement and identify the minimum useful artifacts and stakeholder work.
Standing up or maturing BA
Service model, intake, governance, standards, repository, adoption, decision rights, demand, measures, and where not to overbuild.
CBA concepts and study planning
Distinctions, scenarios, integrated examples, error diagnosis, and study sequence—never recalled exam questions or dumps.
Moving into business architecture
Translate operational, product, process, analysis, strategy, or technology experience into credible BA development and evidence.
SCALE and architecture knowledge
Repository structure, metadata, linkage, retrieval, evidence, guardrails, SharePoint/Copilot patterns, and pilot scope.
Mentoring
Limited, structured mentoring for architect progression.
I reserve a small number of free mentoring relationships for people actively moving into business architecture or expanding their responsibilities as architects.
This is more deliberate than answering a single email. We establish a goal, use the mentee’s own sanitized work or a neutral case, meet around concrete artifacts and decisions, and keep a private record of progress. The aim is progression in practice and judgment—not dependence on a mentor.
A typical pathway
- Baseline the target role, current evidence, and development goal.
- Select a real or neutral architecture scenario.
- Build and critique the minimum artifact set.
- Practice stakeholder explanation and decision framing.
- Address governance, reuse, and operating-model realities.
- Translate the work into a credible development and career narrative.