I help people make complex products and information easier to understand, use and maintain. My work connects the experience someone encounters with the content, decisions and working practices that support it.
Portfolio
d8p: A second brain built to create
An organized body of knowledge is useful when it helps someone make something. I designed d8p’s architecture, content model and working practices to connect reusable context with reviewed output. Explore the decisions, a content-model transformation and a clearly bounded historical synthetic benchmark.
U.S. Bank: An internal product system people could use
Banking teams needed to find and use internal products. Product owners needed practical ways to maintain sales and technical content. My contribution connected the product catalog, adoption experience and content-management work.
Read the public U.S. Bank summary
Make the next decision easier
A useful artifact answers a question and gives someone a way to act. I make the reasoning visible, test the result and keep the people who will use and maintain it involved. See how that shapes my process.
Explore my portfolio or connect on LinkedIn.
About my approach
I work where product, design, content, engineering and delivery meet. I care about the words people encounter, the structures behind those words and the conditions that keep the work useful.
That means considering several people at once: the person trying to complete a task, the author maintaining the content, the stakeholder responsible for a decision and the team delivering the experience. Each holds information the others need.
Make the problem understandable
I like the moment when people with different perspectives begin to see the same problem clearly. My contribution is often a model, a working example or a documented decision that gives that conversation something concrete to work with.
In the U.S. Bank work, product discovery and the work of maintaining sales and technical content belonged in the same conversation. In d8p, I connected the knowledge behind a task with the way its intent, decisions and evidence survive a handoff.
Build the conditions for useful work
I take planning and documentation seriously because the reasoning has to survive the meeting or session in which it was created. A useful record says what someone decided, why it matters and what evidence would make them reconsider.
The practical tools can be simple: an information model, an annotated example, a review checklist or a working agreement. I use them to support judgment. When the process becomes harder to maintain than the work it protects, I look for a smaller version that still preserves the important decision.
Work with people who know something I do not
I bring content strategy, information architecture and interaction design into conversations about product and delivery. Engineers, researchers, legal or compliance specialists and domain experts retain their own responsibilities. Good collaboration makes those boundaries visible and creates ways to resolve the decisions between them.
Feedback earns its place by changing something: a confusing label, a missing state, an unrealistic handoff or the assumption behind an entire approach. My process describes the behaviors and artifacts I use to make that feedback actionable.
Beyond the brief
I enjoy a good conversation as much as a well-framed problem. Whether we are comparing notes on a project or talking over coffee or bourbon, I am interested in the perspective someone else brings.
