About / Career throughline

The work has changed a lot.The question hasn't.

What are people trying to do, and why is this making it harder than it needs to be?

The environments have changed. The underlying work has remained remarkably consistent. The variety is not something to explain away. It is evidence that the capability transfers.

A foundation / Apple

Start with the person, not the prescribed workflow.

Show me what you're doing. Tell me what you're trying to accomplish.

As a technical educator, I learned that different people could reach the same outcome through different valid workflows. The work was not simply teaching features. It was helping someone understand the capability available to them and gain enough confidence to use it.

That foundation carried forward as the work moved from helping individuals operate inside systems to designing and operating the systems themselves.

Selected career moments

Different environments. The same question underneath.

The scale, tools, and subject matter changed. Each environment made another part of the same capability more visible.

Build the system / TheCrew

From individual capability to organizational capability.

I founded and operated a technology-enabled platform and organization, building workflows around onboarding, support, operations, leadership, and self-service.

When teams struggled, the first question was what the process, tooling, information, authority, or expectations around them were making difficult. Leadership also meant giving capable people real authority instead of requiring every decision to escalate.

Nine times out of ten, it's not the people. It's the system.

Work within reality / Consulting

The theoretically ideal solution is not always the useful solution today.

Consulting reinforced the importance of working within real constraints: existing systems, budget, organizational readiness, and available capability.

Sometimes the right answer was making the current system reliable enough to work now, then helping the organization move toward better architecture when it was ready.

The best solution is the one the organization can actually support.

Learn the domain / Litigation technology

Sometimes the capability already exists. The usable system does not.

In litigation technology and information architecture, I entered an unfamiliar domain where the software already contained much of the needed capability.

The work was to understand the goal, learn enough of the domain, identify why the information remained difficult to interpret, and create a repeatable structure and method that made records more recognizable and findable.

Build directly / Broken Compass

Definition, implementation, testing, and enablement now meet in the same work.

Broken Compass is a pre-launch multiplayer roleplay platform. It represents another evolution: I now directly build many of the capabilities I once would have defined, requested, tested, documented, or operationalized with a development team.

Product behavior, technical implementation, workflow design, documentation, administration, testing, governance, and user experience increasingly meet in the same work.

Working together

I don't need to be the expert in everything. I need access to the people who are.

Subject-matter expertise matters. When I enter an unfamiliar environment, I talk with the people closest to the work and ask them to show me their world. I need to understand what they own, what they are trying to accomplish, where they are frustrated, and what constraints I may not see yet.

They bring the domain expertise. I bring a systems perspective and help connect what they know across products, processes, information, tooling, and organizational boundaries.

“How has anyone been putting up with this?”

The more useful next question is: why have they had to?

I am inquisitive, direct, and comfortable asking basic questions when basic questions are necessary. I would rather see the actual process than perform certainty about how it is supposed to work.

I work well with autonomy and clear ownership, collaborate across disciplines without needing every contributor to report to me, and will challenge an assumption, including my own. I am also comfortable saying I do not know something yet.

The goal is to leave people with greater capability, not to make myself a permanent dependency.

What comes next

A full-time role with a meaningful problem to own.

I am looking for a full-time role involving some combination of knowledge systems, customer or employee enablement, AI enablement and adoption, operational improvement, business systems, product or platform operations, and systems and experience strategy.

The exact title matters less than the problem and the access and authority required to work on it. A strong environment lets me understand the actual system, talk with the people closest to the work, investigate before guessing, and carry improvements far enough to learn whether they actually work.

Michigan US Remote

Start a conversation

Got a messy system? I'd like to hear about it.

If you are hiring for a full-time role with a complicated professional problem that needs real ownership, tell me what is getting in the way.

Email DebraView Résumé