To be clear: what you get from hiring me is understanding that can be shared.

Sometimes it’s making sense of something that’s been hot-fixed into chaos and/or dysfunction
Sometimes it’s adding depth or nuance or interoperability
Sometimes it’s articulated for the first time
The sharing can be internal or external; to a decision maker, team, and/or business

Understanding is the key to building, processing, and changing.

The artifacts are there to help share the understanding, so they shift with what understanding needs to be shared, with whom. I’m constantly tailoring and refitting artifacts to the understanding at hand, and often to the audience (writ big) or people (writ nuanced) who are involved. When the build or change is extensive, the artifacts often need to come with a library, to better be able to navigate to the piece that’s helpful right now.

—-

Artifacts

Diagrams & flows
Spreadsheets, Baserow/Airtable
Presentations
Libraries
Wireframes
UX design files
Conceptual writing

—-

Common project types

Domain mapping
Product management and design
Process & logic design
Project management & design
Metadata and taxonomy
Internal navigation
Design architecture
Design system infrastructure
Accessible design
Content management
External navigation

—-

Expressed as

Applications
Websites
Sales enablement
Cross-functional backoffice process

—-

Industry agnostic, with industry tendencies

I learn for a living, and I’ve figured out how I learn – for me, it’s all about systems thinking. When a project starts, I use an internalized and highly fungible version of domain mapping to get my sense of orientation.

Industries I’ve spent significant chunks of time in:

Investment management
Agency
Privacy & personal information
Healthcare

This is not a robust list; the last time I tried to sit down and count, it was around 15 industries. My expertise is information structures and human cognitive behavior. I trust and depend on subject matter experts and information literacy.