"The Hell It Is." — How a Wall of Post-It Notes Sparked a Culture of Continuous Improvement
On my first day in a new role, I watched managers run their entire operation off hand-transcribed sticky notes. That was the moment I knew exactly what needed to change — and how.
May 24, 2026
Lean/CI, Operations, Change Management, Leadership, Cross-Industry
The Observation
I was approximately one hour into my first day as a Retirement Operations Manager at Global Atlantic when I stopped walking and watched something that fundamentally set the trajectory of my next five years at the company.
A manager was hunched over her workstation, manually transcribing data from an antiquated legacy system — field by field, number by number — onto Post-It notes. Those Post-It notes went on a wall. That wall was the operational command center for her entire team. Every morning started with this ritual: pull the data, transcribe it by hand, stick it to the wall, then use the wall to assign work, track progress, and manage throughput for a 50-person retirement operations team handling a rapidly growing book of business.
I asked her what she was doing and why.
She told me it was the only possible way available. The legacy system didn't surface the data in any usable, real-time format. There was no dashboard. No automated reporting. No live operational view. The system held the data hostage behind an interface that was never designed to support dynamic operational management. So she built her own system — out of sticky notes, a Sharpie, and daily manual effort.
The Response
I said the hell it is.
Not confrontationally. Not dismissively. But with the absolute certainty that there was a better way — because there's always a better way when the current process involves a human being manually transcribing digital data onto paper so that other humans can read it off a wall.
That moment — that single observation on my first day — kicked off a progression that would take me from operations manager to Salesforce power user to the company's go-to person for reporting and dashboards to a formal Continuous Improvement role applying Lean Six Sigma methodology across the enterprise.
None of that was in the job description when I started. All of it grew from refusing to accept a Post-It note as a permanent solution.
Diagnosing the Gap
Before building anything, I needed to understand why the gap existed. Not just the surface-level "the system doesn't do it" answer — the systemic reasons why a team of professionals in a major financial institution was operating off handwritten notes in 2018.
The root causes were layered. The legacy administration platform was a third-party system designed primarily for policy servicing and transaction processing — not for operational visibility or management reporting. Its native reporting capabilities were rigid, batch-oriented, and required technical expertise to customize. Nobody on the operations team had been trained to build reports within it. Nobody on the technology team had been asked to build operational dashboards for the operations floor because the operations team had never formally articulated the requirement. They'd just adapted — built a manual workaround and normalized it over time.
The gap wasn't technical impossibility. It was a communication failure between operations and technology, compounded by years of operational teams solving their own problems with whatever was available rather than demanding better tooling.
The First Build
I started by going directly to corporate leadership with pointed questions: why do we not have real-time operational visibility? What are the actual constraints? What's technically possible within the systems we already own?
The answers I got back confirmed what I suspected — the capability existed, but nobody had asked for it in a way that connected the operational need to a specific technical request. So I drafted a sample dashboard concept — a visual mockup of what I needed the data to look like — and sent it to our third-party administrator with a simple question: can you build me this?
They did. Bare bones. Functional but limited.
I immediately followed up: can I build my own? Give me the access and permissions to create reports and dashboards directly within the platform.
They did.
Self-Taught Platform Mastery
What followed was an accelerating cycle of self-taught capability development. I didn't have Salesforce training. I didn't have a reporting background. What I had was a clear operational need, direct access to the platform, and a willingness to figure it out through iteration.
I built the first operational dashboard within the first few weeks — replacing the Post-It wall with a live, auto-refreshing view of the same data that had previously required daily manual transcription. The team's reaction was immediate: they could see their work in real time. Bottlenecks were visible. Throughput was measurable. The manager who had been transcribing data every morning could now spend that time actually managing her team.
From there, the requests started coming. Other managers. Other teams. Other business units. "Can you build me this? Can you modify that? Can you create a view that shows me X?" Every request expanded my capabilities within the platform and expanded the organization's understanding of what was available to them inside tools they already owned.
Formalizing the Methodology
As the dashboard and reporting work matured, the natural next question emerged: now that we can see the data clearly, what does it tell us about where the process is actually breaking down?
That's where Lean Six Sigma entered the picture. The reporting infrastructure I'd built gave us visibility. DMAIC gave us methodology. I began applying formal Continuous Improvement frameworks to the workflows we could now measure accurately for the first time:
Define — identify the specific process bottleneck or inefficiency using the operational data now available through the dashboards.
Measure — establish baseline performance metrics. For the first time, we had clean data on cycle times, handoff durations, error rates, and throughput by process segment.
Analyze — trace the root causes of the measured inefficiencies. Where were handoffs creating delay? Where were rework loops consuming capacity? Where were process steps adding time without adding value?
Improve — redesign the workflow to eliminate identified waste. Streamline cross-functional handoffs. Remove redundant approval steps. Automate notification and routing where manual intervention wasn't adding decision value.
Control — implement monitoring through the same dashboards that identified the problem, creating a sustained feedback loop that prevented regression and enabled continuous measurement.
The transition from "the dashboard guy" to a formal Continuous Improvement Operations Manager was a natural evolution — one that the organization recognized and resourced because the results were already visible before the title change ever happened.
Quantitative Results
The Lean methodology applied against our newly-visible process data produced measurable, sustained improvements:
Operational cycle time reduced from 4.7 days to 3.6 days — a 23% improvement. This metric captured the full duration from case initiation through completion across the retirement operations workflow. A full day removed from the average cycle directly improved client experience, reduced downstream rework triggered by delays, and increased team capacity without adding headcount.
Application-to-issue time reduced from 7 days to 5 days — a 29% improvement. This was the client-facing metric that mattered most to the business: how long a client waited from application submission to policy issuance. Reducing that by two full days represented a tangible competitive advantage in a market where client experience increasingly drives retention and growth.
Cultural Transformation
The metric I'm most proud of doesn't live on a spreadsheet.
When I started, one manager was transcribing data to Post-It notes because she believed it was the only possible way. By the time the Continuous Improvement work was mature, managers across multiple business units were proactively requesting new dashboards, identifying their own process inefficiencies, and bringing data-driven improvement proposals to leadership without being prompted.
That cultural shift — from passive acceptance to active improvement-seeking — is harder to manufacture than any process redesign. People who once said "this is the only way" were now the ones demanding better tools, clearer data, and faster processes. They weren't doing it because someone mandated a CI initiative. They were doing it because they'd seen what was possible, experienced the benefit directly, and developed an appetite for more.
Job Security Through Value Creation
There's a practical dimension worth acknowledging: I grounded my job security in what I was able to support across business units. Every dashboard built, every report configured, every process improvement delivered created organizational dependency on the capability I was providing. That wasn't accidental — it was deliberate positioning. When you become the person who makes everyone else's job easier and more visible, your value transcends any single role description.
That positioning eventually created the cross-functional visibility that led to the Salesforce Working Group, which led to the AVP role, which led to AI. The seeds of the entire subsequent career progression were planted in the decision to refuse a wall of Post-It notes as acceptable.
Quantitative Results
The Lean methodology applied against our newly-visible process data produced measurable, sustained improvements:
Operational cycle time reduced from 4.7 days to 3.6 days — a 23% improvement. This metric captured the full duration from case initiation through completion across the retirement operations workflow. A full day removed from the average cycle directly improved client experience, reduced downstream rework triggered by delays, and increased team capacity without adding headcount.
Application-to-issue time reduced from 7 days to 5 days — a 29% improvement. This was the client-facing metric that mattered most to the business: how long a client waited from application submission to policy issuance. Reducing that by two full days represented a tangible competitive advantage in a market where client experience increasingly drives retention and growth.
Cultural Transformation
The metric I'm most proud of doesn't live on a spreadsheet.
When I started, one manager was transcribing data to Post-It notes because she believed it was the only possible way. By the time the Continuous Improvement work was mature, managers across multiple business units were proactively requesting new dashboards, identifying their own process inefficiencies, and bringing data-driven improvement proposals to leadership without being prompted.
That cultural shift — from passive acceptance to active improvement-seeking — is harder to manufacture than any process redesign. People who once said "this is the only way" were now the ones demanding better tools, clearer data, and faster processes. They weren't doing it because someone mandated a CI initiative. They were doing it because they'd seen what was possible, experienced the benefit directly, and developed an appetite for more.
Job Security Through Value Creation
There's a practical dimension worth acknowledging: I grounded my job security in what I was able to support across business units. Every dashboard built, every report configured, every process improvement delivered created organizational dependency on the capability I was providing. That wasn't accidental — it was deliberate positioning. When you become the person who makes everyone else's job easier and more visible, your value transcends any single role description.
That positioning eventually created the cross-functional visibility that led to the Salesforce Working Group, which led to the AVP role, which led to AI. The seeds of the entire subsequent career progression were planted in the decision to refuse a wall of Post-It notes as acceptable.
Reflection
We have a saying in the Army: always be improving your position. In combat, that means a deeper foxhole, better concealment, stronger cover. Every hour you're static, you should be making your position harder to overrun.
In the professional world, the stakes are different but the mindset is identical. How did I survive yesterday? What can I do better to ensure I survive tomorrow? What's the thing I'm tolerating right now that I shouldn't be tolerating — and what would it take to fix it?
A wall of Post-It notes wasn't the enemy. Accepting it as permanent was. Every improvement in this story started with the same question: why is this the way it is, and does it actually have to be?
The answer, in my experience, is almost always no. The constraint is rarely technical. It's usually a combination of awareness, initiative, and the willingness to build the solution before anyone asks you to.
The Principle
Work smarter, not harder. But understand that "working smarter" often means doing more work upfront — building the tool, teaching yourself the platform, making the case to leadership — so that the sustained daily work becomes dramatically more efficient. The investment is front-loaded. The returns compound indefinitely.
This project connects directly to my work in Continuous Improvement & Lean Operations, Operational Integration & SOP Development, and Training & Change Management — the same combination that later became the foundation for everything I built in AI strategy.