Skip to main content

Problem Solving

A lot of the work I’m drawn to does not start with a clean brief.

It starts with some mix of these:

  • scattered information
  • inconsistent structure
  • unclear ownership
  • underexplained workflows
  • fast-moving source material
  • too many stakeholders
  • not enough shared understanding

That is the kind of problem space where I tend to be useful.

How I usually approach it​

First, identify the actual problem​

A documentation request is not always just a documentation request.

Sometimes the real issue is:

  • poor structure
  • fragmented process knowledge
  • weak discoverability
  • conflicting assumptions
  • content that reflects internal complexity instead of user needs

I like identifying the real problem before I start polishing text.

Then, find the stable patterns​

When information is uneven, I look for what repeats:

  • recurring questions
  • repeated workflow gaps
  • similar content types
  • places where users get stuck
  • knowledge that exists but is hard to reuse

That gives me a starting point for structure.

I also pay attention to where people naturally go for help. A lot of the time, they do not start with formal documentation. They ask another person, search informally, or look for examples from someone who has already solved the problem. That matters, because good documentation should account for how people actually seek help, not just how we wish they would.

Then, build something people can use​

I care less about theoretical elegance than whether the result actually helps.

That might mean:

  • restructuring content
  • introducing a repeatable page model
  • clarifying steps
  • defining terms
  • improving navigation
  • using analytics to support better decisions
  • building lightweight supporting systems when needed

What this looks like in practice​

In my work, problem-solving has included:

  • documenting complex hiring workflows for Meta’s Recruiting Management Software
  • leading documentation support across more than 100 products
  • implementing documentation analytics using Tableau
  • streamlining reporting processes with Excel and structured data work
  • onboarding acquired products into established documentation practices
  • helping drive DITA and XML adoption
  • turning community chat content into structured help through TeraCreators Help

What I bring​

I bring a mix of writing, judgment, structure, and persistence.

I’m comfortable entering projects that are still fuzzy, learning the shape of the system, identifying what matters, and building a clearer path forward.