SELECTED WORK / INFORMATION ARCHITECTURE
Making complicated systems easier to navigate.
I approach architecture by understanding what exists, tracing how the pieces connect, and designing a structure people can actually use and maintain. These projects span multi-location websites, WordPress development, and AI-assisted operational workflows.
01 / LARGE-SCALE INFORMATION ARCHITECTURE
Thompson Law
From inconsistent geographic URLs to a defined page hierarchy.
The challenge
A large legal website expanded across states and cities without a consistently expressed geographic hierarchy. Older URL patterns varied by city, state, and practice, making page relationships, mapping, and location-based reporting difficult to manage.
My contribution
Researched and helped establish a national → state → city/office → practice-area structure; worked on URL mapping and redirect planning; coordinated internal-link priorities and technical validation across the migration.
Consistent geographic paths, clear parent/child intent, documented legacy mapping, and validation of redirects, canonicals, navigation and internal linking.
The geographic hierarchy and migration planning are documented, but subsequent performance was affected by overlapping site changes and reported server, crawling, and caching incidents. No single cause of the search decline or ranking recovery is established by this case study.
02 / MULTI-LOCATION HEALTHCARE
Premier Injury Clinics
Reorganizing what already exists before creating more.
The challenge
An outside audit recommended more location pages and substantially more copy. My review of the existing site found location pages and extensive content were already present, but page overlap, weak organization and inconsistent visitor pathways called for a different priority.
My contribution
Reviewed the audit against existing pages; separated useful recommendations from unsupported assumptions; proposed a structure built around locations, treatment services and injuries, supported by blogs and contextual links.
Supporting articles connect visitors to the relevant location, treatment, and injury information.
Audit existing URLs → decide which pages to retain or consolidate → finalize redirects and primary destinations → organize internal links → expand only for verified gaps.
The audit review and architecture proposal are documented. The site underwent repeated design changes, limiting the time available to measure any one version consistently. Early improvement is reported, but its extent and attribution require dated change and Search Console comparisons.
03 / HANDS-ON WEBSITE DEVELOPMENT
Owl Pipe ID
Hands-on ownership in an established WordPress site, with later search visibility to investigate.
The challenge
Extend an existing business website without making the new experience feel disconnected from the site's established structure and visual conventions.
My contribution
Worked within the WordPress environment to add a Free Samples page and form, reuse familiar site components, and maintain continuity with the navigation and existing layouts.
Study the existing components → identify the page's role → build within reusable patterns → check content and form behavior.
In a six-month Google Search Console view shared November 2026, the website recorded 18.2K impressions, 167 clicks and an average position of 16.9. The chart shows a later increase in visibility; it does not isolate the effect of this page/form work or establish lead conversions.
04 / OPERATIONAL SYSTEM DESIGN
Vito / Lucky OS
Designing technical workflows that preserve evidence and require validation.
The challenge
Recurring audits and investigations produce large amounts of evidence, interrupted work, competing hypotheses and proposed changes. Without a durable process, it's easy to repeat work or mistake a prepared change for a verified fix.
My contribution
Defined an investigation and operations workflow emphasizing source traceability, checkpoints, change status, review gates, and clear separation between analysis and production implementation.
Keep observations distinct from hypotheses, mark unresolved findings honestly, retain recovery checkpoints, and require authorization before live changes.
Ongoing system design and development. The workflow documentation supports the design approach, not a claim of fully autonomous production deployment.