Process

How I think through projects and solve problems.

Learning design Motion systems Interactive web AI enablement

This page explains the kinds of problems I am best suited to solve, how I choose the right medium, and the principles I use to turn a complex workflow or idea into something clear, useful, and reusable.

Typical first phase: understand the workflow, choose the medium, and build the clearest first version.

Problem framing

The problems I like to solve.

These are usually moments where motion, interface storytelling, or interactive structure can do more than static documentation alone.

A workflow is documented but still hard to follow

The process exists on paper, but the sequence, emphasis, or decision points still are not landing clearly in practice.

A product or system needs a clearer explanation

The feature set is there, but people still need a clearer story for what matters, how it works, and how to move through it.

The launch story explains the change, not the moment of use

Announcements or campaign assets describe what is new, but not what it feels like to complete the task or navigate the interface.

AI or new tooling still feels vague

Teams need grounded examples, safer guidance, and a more concrete way to connect the new tool to real work.

Capabilities

The types of work this portfolio is built around.

Motion + onboarding

Workflow explainers

Short visual assets showing how a system, workflow, or decision path works when a static explanation is not enough.

  • Storyboarding and scripting support
  • Motion-led walkthroughs and microlearning
  • Reference assets or support layers
  • Reusable visual structure for follow-on modules

Best for software onboarding, feature explanation, workflow adoption, and rollout communication.

View projects

Interactive web

Learning and campaign experiences

Web-based experiences that help people explore, revisit, or engage with an idea more actively than a single video or deck allows.

  • Interactive learning or campaign sites
  • Guided decision paths and lightweight scenarios
  • Reference views that support repeat visits
  • Design patterns that can scale across pages or phases

Best for onboarding hubs, campaign experiences, interactive learning, and internal communication surfaces.

View projects

AI + enablement

AI adoption and guidance

Practical examples and training content that make emerging AI tools feel more concrete, usable, and connected to actual work.

  • Task-based AI use cases
  • Safer-use guidance and framing
  • Manager-friendly examples and support assets
  • Repeatable structures for future enablement content

Best for internal AI pilots, employee guidance, practical experimentation, and emerging-tool onboarding.

View projects

Systems thinking

Launch support ecosystems

Projects where motion, job aids, intranet pages, and communication assets need to feel connected instead of acting like separate pieces.

  • Modular asset planning and alignment
  • Reference support around a core experience
  • Visual consistency across channels and formats
  • Patterns that scale past the first launch or project

Best for rollouts, internal programs, campaign systems, and multi-asset initiatives that need one visual logic.

View projects

Process

A simple structure I use to turn complex material into something clearer.

01

Find the friction

Start with the user action, the blocked moment, and what still feels harder than it should.

02

Map the workflow

Map the sequence, decision points, and moments that need clarity before building.

03

Build the useful core

Build the smallest asset or experience that makes the idea clearer without overbuilding it too early.

04

Ship it where needed

Package the work so people can reach it where they actually need it, then expand it over time.

Medium Logic

How I think about format, not just deliverables.

When motion helps

  • You need pacing, emphasis, and a clearer sequence
  • An interface or process should be shown, not just described
  • The story needs visual hierarchy and a stronger rhythm

When interaction helps

  • People benefit from exploring, revisiting, or self-pacing the material over time
  • The explanation works better as a surface than a single asset
  • The project needs a structure that can grow across pages, states, or phases

Selected projects

See all projects

Contexts

Where this kind of work tends to fit well.

Project contexts

  • Software onboarding and internal tool adoption
  • Launch communication and workflow explanation
  • Interactive learning, campaign, and scenario-based experiences
  • Practical AI enablement and emerging-tool guidance

What usually matters most

  • The explanation needs a stronger medium choice
  • The work should feel clear fast, not just complete
  • The first version needs room to become a larger system later
  • Structure, pacing, and usability matter as much as the content itself

Working Notes

A few notes on how I usually approach collaboration.

What do you need to start exploring a project?

A topic, audience, context, and one place where clarity is breaking down usually are enough to start a useful conversation.

Do you only work in one medium?

No. The medium follows the problem. Some ideas need motion, some need interaction, and some need a connected system of assets.

Can this plug into an existing team or system?

Yes. The work can align to existing brand, product, learning, or communication systems rather than starting from scratch.

Do projects usually stay one-offs?

Often they start with one asset or surface, then expand into a repeatable pattern once the first version proves useful.

Contact

If a project needs clearer motion, structure, or interaction, that is usually where I am happiest to help.

I am especially drawn to projects that need a sharper medium, a clearer system, or a more thoughtful way of guiding people through the experience.