Home / Selected Artifacts
Selected Work

Selected Work

Each of these artifacts shows how I structure the work behind a solution: the metadata models, testing frameworks, delivery infrastructure, and communication layers that make implementation possible. Not all of them reached launch, but each one reflects how I approach the problem-framing and operational design that comes before it. All screenshots are representative artifacts with sensitive information redacted.

01
Knowledge access

Designing cleaner ways to surface documents, structure metadata, and reduce search friction.

02
Structured testing

Creating clear validation frameworks so complex workflows behave as expected before launch.

03
Vendor rollout management

Building the dashboard, trackers, and reporting structure that kept rollout work visible and moving.

04
KM adoption communications

Using a structured internal publication to surface tools, training, and knowledge resources in one place.

Artifact 01

Knowledge search interface and metadata structure

Attorneys often know the kind of document they need, but not where it lives or what it is called. To reduce that friction, I worked with an internal IT team to connect our DMS to Smartsheet and then connect that structured information more user friendly search experience.

I also helped shape the underlying metadata model, including opportunities to leverage automation to generate additional metadata so the collection stays current without requiring constant manual intervention.

Redacted metadata table showing document number, version, name, last edit date, parent folder, folder path, link, practice area, document type, description, authors, review cycle, and first-year collection fields.
Underlying metadata structure
A structured layer that makes the collection easier to filter, govern, review, and extend with automation.
Search interface with filters for practice area, collection inclusion, last edit date, and a searchable list of document records.
Attorney-facing search interface
The result was a more navigable collection that attorneys could search without needing to know the DMS folder structure, reducing dependence on Knowledge staff for routine document retrieval and making the collection more self-sufficient over time. The project did not reach launch, but the design reflects how I approach building access layers that can scale without heavy staff involvement.
Artifact 02

Workflow testing matrix

During the development of a complex knowledge repository project, which was worked on by our IT professionals, vendors, and consultants, I developed a structured testing matrix to test that workflows behaved as expected.

The matrix made it easier to validate scenarios by function and user role, document expected outcomes ahead of time, and keep implementation feedback visible so it could be reviewed and acted upon.

Redacted testing matrix with columns for function, row ID, persona, scenario, expected result, pass or fail, and testing notes.
Structured testing matrix
The matrix gave the implementation team a shared source of truth during a high-pressure rollout. Issues were caught before launch rather than after, and the structured format made it easier to demonstrate readiness to firm leadership. The broader project did not reach completion, but the matrix did its job.
Artifact 03

Vendor rollout project management

For a document automation platform rollout, I helped create a centralized dashboard that tracked project tasks, migration status, bugs, enhancement requests, tester feedback, and team updates in one place.

This work was done directly with the vendor and a dedicated internal team spanning multiple departments, making it easier to coordinate activity, maintain visibility, and keep work moving across a complex implementation.

Redacted implementation dashboard with sections for tasks, team announcements, important links, migration updates, bug reports, general questions, enhancement requests, and tester feedback.
Vendor rollout dashboard and supporting trackers
This artifact shows the editorial structure and format I designed for a quarterly internal KM & Innovation publication. The goal was to create a repeatable communication layer: one that could surface tools, training, and knowledge resources consistently rather than relying on email announcements. The project did not reach launch, but the design reflects how I think about making KM programs visible and sustainable over time.
Artifact 04

KM & Innovation communications

This redacted flipbook captures a quarterly internal KM & Innovation publication designed to improve visibility into training, legal tech updates, research resources, and internal tools.

I would position this less as a newsletter and more as a structured adoption artifact: a repeatable communication layer that helps people understand what resources exist, why they matter, and where to go next.

Redacted KM & Innovation publication
Example internal KM publication presented as a redacted video artifact. Sensitive details and personnel information have been removed.