Buildingorganisations.
Some people build software. Others build companies. Others build communities. For more than forty years I have been building organisations — small businesses, municipalities, government departments, community organisations, startups. The role never changes: understand the problem, simplify the situation, put a structure in place that will hold.
- 01TechnologyAzure, Entra ID, security, AI
- 02GovernanceBoards, bylaws, compliance
- 03LeadershipDirection, decisions, growth
- 04CommunityNon-profits, volunteers, mission
- 05PeopleWhat everything else serves
- 40+ yrs
- Leadership and entrepreneurship
- 35+ yrs
- Information technology
- 1,000+
- Talks and training sessions
- 38
- Documented architecture engagements
None of these skills on its own
Cybersecurity experts exist. So do seasoned entrepreneurs. So do speakers who can hold a room. Taken separately, none of that is rare.
What is rarer is being able to work on an identity architecture in Microsoft Entra in the morning, revise a community organisation’s bylaws in the afternoon, and make the same person understand both.
These worlds almost never talk to each other. Technology people find governance slow; governance people find technology opaque; the community sector feels shut out of both. My work is taking those walls down — and it is why people call.
Where to start
Depending on what brought you here: my path and how I work, the fields I work in, or the organisations I have built.
«I say what I do and I do what I say.»
Field notes
Let’s talk about what you want to build.
An organisation to structure, infrastructure to take back under control, an AI project that needs guardrails, a board to equip, or a room to win over. Tell me what you have in mind.