I turn operational friction into systems teams can actually use.

I’m Chris Lovallo—a Facilities Planning Analyst and solutions builder working where frontline operations, product, and engineering meet.

Explore the Workbench See how I work

Frontline-informed
Modular by design
Validation-led
Built for real constraints

System topology // 08 workflow lanesEight operational jobs. One shared operating layer.

Authorized inputOperator selections · Structured files · Existing systems

01Asset GridBulk export, edit, validate, and return asset records.Export ⇄ Return

02Project ScheduleReview and update project records in controlled batches.Export ⇄ Return

03CWI Creation + PortabilityCreate structured CWIs and analyze reuse across institutions.Structure → Compare → Create

04Modeled AssessmentsBuild repeatable assessments from structured building inputs.Inputs → Assessments

05Image ManagementExport, upload, relink, and recover facility images.Media ⇄ Links

06ROPA IntegrationDownload, validate, transform, and upload planning records.Download ⇄ Upload

07Data RepairDetect mismatches, remap classifications, and verify corrected state.Inspect → Correct → Verify

08Field QCSurface missing images, classifications, and dependencies before handoff.Scan → Flag → Handoff

Shared operator surfacePlanning Services
Workbench

01Preview
02Validate
03Execute
04Recover

Verified returnOutcome confirmed against the authoritative system

Operational telemetry // Live

Make the system visible before changing it.

My work starts by observing the real workflow—its signals, constraints, failure modes, and the people operating inside it. Measurement turns that evidence into a path forward.

Flagship system

Planning Services Workbench

One operator-focused system for recurring planning workflows, with every capability independently measurable.

I designed it from inside the work. Each module addresses a distinct failure point; the Workbench turns those solutions into a repeatable operating layer with shared patterns, validation, and recovery.

View the full case study

Built from inside the problem

Planning work moved between browser tools, spreadsheets, manual transformations, and repeated handoffs. The product thesis was simple: solve each failure point, then unite the solutions behind one shared operator surface.

One system. Independently measurable capabilities.

Workbench succeeds as a unified product, but every capability must prove its own value.

CAPABILITY // 01MATURITY // PROTOTYPE

Asset Grid

Snapshot

Edit

Validate

Verify

Operational job: Bulk export, edit, validate, and return asset records without trusting an unreliable save path.
Current evidence: The prototype preserves a local snapshot, applies field-level checks, and verifies the returned state.
Measurement focus: Task time, records per run, validation issues intercepted, confirmed returns, and recovery events.

ContributionWorkflow discovery Requirements Architecture Implementation Testing Cross-functional alignment

Lovallo OSSelected work // Method

Selected Work

01Integration Capability AssessmentMapped authentication behavior, documentation gaps, and a responsible integration path.Investigation · Validated 02Rapid Record-Entry AutomationTurned a repeatable creation task into a structured, working workflow.Utility · Working 03Facilities Data Quality WorkflowConverted recurring QC findings into ownership, validation, and correction rules.Operating model · Defined

How I build

From observed friction to a system other people can use.

01Observe
Understand how people actually work.
02Measure
Collect evidence before deciding what needs fixing.
03Diagnose
Find the real constraint instead of treating symptoms.
04Architect
Map how users, data, systems, authentication, and constraints interact.
05Build
Create the smallest useful solution that makes the path concrete.
06Validate
Test real conditions and measure whether the workflow improved.
07Integrate
Turn successful solutions into dependable, reusable systems.

Recognition in practiceTechnology · Product · Architecture · Engineering · Operations

Responsibility followed the work

The pattern is visible beyond the work itself.

Across collaboration with senior leaders and partners, the same strengths have been recognized repeatedly—not through testimonials, but through the technical ownership, review, and strategic responsibility that followed.

Engineering mindset: Approaching operational problems through systems, interfaces, failure modes, validation, and maintainability.
Inventive execution: Finding practical paths through enterprise constraints and turning ambiguous problems into working, testable solutions.
End-to-end ownership: Carrying work from investigation and requirements through architecture, implementation, evidence, and alignment.
Cross-functional translation: Connecting frontline reality with product direction and engineering constraints so different teams can act together.
Strategic range: Contributing beyond traditional analyst responsibilities by identifying reusable opportunities and sustainable technical ownership.

Workbench is not an isolated build. It is the clearest evidence of a way of operating that others have already recognized.

Lovallo OSPosition // Writing // Contact

Domain analyst by role. Solutions architect by method.

My current title is Facilities Planning Analyst. My work increasingly resembles solutions engineering: understanding the operator’s problem, translating it into technical requirements, building a working path, and aligning operations, product, and engineering around what comes next.

Solutions ArchitectureSolutions EngineeringTechnical Product Operations

Writing 01Developing in an Ever-Changing AI Climate