01 / EMPLOYEE EXPERIENCE / INTERNAL OPERATIONS

LP Switchboard

Local Projects' internal operations platform

What started as a clearer way to reach Operations evolved into a broader employee-facing system connecting services, requests, equipment, purchasing & operating guidance.

THE QUESTION BEHIND THE BUILD

What if the right starting point wasn't another inbox?

EmployeesRequestsRole-aware access
CONTEXTLocal Projects
AUDIENCE75+ employees + extended workflows
OWNERSHIPDiscovery → build → administration

01 / THE CONTEXT

One place for the work that keeps things moving.

The same questions kept showing up in different places. Requests arrived through separate channels. Knowledge lived in spreadsheets, administrative consoles & individual memory. Even the straightforward tasks depended on knowing who to ask.

The original goal was better communication between employees & Operations. As the patterns became clear, the more useful answer was a connected operating layer for the work itself.

02 / THE EXPERIENCE

Built around how
people actually work.

Select a design decision to explore what the interface was intended to make easier.

LP Switchboard screenshot showing employee navigation, IT, equipment, purchasing, events & facilitiesClick to inspect
Employee-facing home screen. Company-specific navigation & requests organized around everyday work.
DESIGN DECISION

A useful starting point

The experience is organized around what employees need to do, not around which administrative system owns the task.

03 / WHAT I OWNED

From discovery to the operating details.

01 / DESIGN

Understand & structure

Mapped real requests, dependencies, decisions, roles & information. Defined navigation, business rules & source-of-truth relationships.

02 / BUILD

Implement & verify

Directed AI-assisted development, workflow & permission logic, testing, troubleshooting & iteration against actual tasks.

03 / HANDOFF

Make it maintainable

Considered training, administration, user support, documentation & how a changing organization would extend the system.

04 / WHAT IT DEMONSTRATES

Scaling isn't always about more people. Sometimes it's about letting the same organization do more, with better coordination & less dependency on any one person.

EXPANDING TO NEED / NOT JUST HEADCOUNT

Scope note: this case demonstrates operating design & documented capabilities, not a claim of independently verified enterprise-scale load or utilization.

CONTINUE EXPLORING / NEXT CASE

Ask A Local
02 / 05