04 / About

Across disciplines.

I write, design, and build systems—turning complex ideas into work people can understand and use.

Writing · Design · Technology · Research · Strategy

The Throughline

One career. Several disciplines.

I started in technology, where writing a manual, training a room, troubleshooting a system, and improving the process around it could all be parts of the same day. Over time, that work expanded into web development, research, UX, editorial design, healthcare decision support, and creative work.

The disciplines changed. The questions did not. What is this really trying to do? Who needs to understand it? What is getting in their way? What form will make it clearer? What system will keep it working?

I’m usually most useful at the boundaries—where a story becomes an interface, an interface becomes a system, or a system needs to make sense to a human being.

How I Work

The medium changes. The approach is consistent.

I like work that rewards curiosity, close attention, and the ability to move between the details and the whole system without losing either.

01

Start with the real problem.

The request is not always the problem. I want to understand the people, constraints, workflow, and outcome before choosing a tool or medium.

02

Translate between disciplines.

Writers, designers, researchers, developers, support teams, and clients often describe the same problem in different languages. I am comfortable working between them.

03

Make complexity legible.

Whether it is a story, an interface, a research project, or an infrastructure problem, the goal is to reveal the structure without flattening what matters.

04

Leave a better system.

A good solution should still work after the immediate problem is gone. Documentation, maintainability, training, and process are part of the work.

Selected Path

A career built in the overlap.

This is the short version—not every title or project, just the shifts that explain how the disciplines on this site ended up belonging together.

1998—2005

Keane, Inc.

IT Management · Application Administration · Technical Writing · Training

Multi-office systems, infrastructure, application support, technical documentation, training, and development-team work established the pattern early: technical problems rarely stay inside a single job description.

2005—2010

Dartmouth College

Student IT Services & Public Computing

Managed support operations for a large student community, hired and trained support staff, and built a custom computer-imaging workflow that dramatically reduced recurring system-preparation labor.

2010—2012

Dartmouth Psychiatric Research Center

Web Development · Research Systems

Moved deeper into the overlap between technology, design, and research: enterprise websites, interface redesign, QA, user support, and an internal project-management system.

2012—2015

The Dartmouth Institute

IT Support Management · Systems · Process

Supported an academic research environment while building services around secure infrastructure, authenticated cloud storage, video, onboarding, training, and process improvement.

2015—Now

Veracity by Design

Creative & Technical Direction

Independent work spanning healthcare decision aids, research collaboration, web and identity design, technical strategy, support, content, and implementation—alongside fiction, editing, and music projects.

Education

Writing taught me to look closely. Technology taught me to trace causes.

Design lives comfortably between those habits: paying attention to what people experience while understanding the structure underneath it.

2012

MFA · Creative Writing

University of Southern Maine

Stonecoast MFA program, with a specialization in popular fiction.

1998

BA · English

Plymouth State University

Creative writing, literature, philosophy, and visual-art/design study.

Where I Fit

Some projects need a specialist. Some need someone who can connect the specialists.

That second kind of project is usually where I’m most useful: work that needs strong language, thoughtful design, technical understanding, and someone willing to keep asking how the pieces affect one another.

Accessibility

This site is being built with semantic structure, keyboard access, visible focus states, sufficient contrast, responsive text, and reduced-motion support as core requirements.

Privacy

The site is designed to collect as little information as practical. A launch privacy statement will document any analytics or contact services actually in use.