Decide once, render everywhere
When five channels each interpret the same data, they drift. I look for the one place a decision belongs, put it there, and let every channel show the finished answer.
Product, Technology & Business Strategy Leader
15+ years turning big ideas into things people actually use, across agencies, global manufacturing and insurance. At Unum I advise IT leadership on a $20–24M technology portfolio, set up AI governance as the first use case on the Monitaur platform, and deliver platforms for 65,000+ active digital users and 1,000+ contact center agents. Customers don’t wake up wishing for a better website; they’re trying to get something done. I take the friction out of that, and I like rolling up my sleeves with engineers to build it, including with Claude Code.
Outside work I advise and teach at a youth robotics organization, and live in Southern Pines, North Carolina, usually camping, hiking or fishing with a good coffee in hand and barbecue never far behind.
Open to Director and AVP roles in product, technology and business strategy
The same handful of habits show up in every product below. They are what I would bring to a new team.
When five channels each interpret the same data, they drift. I look for the one place a decision belongs, put it there, and let every channel show the finished answer.
Wording and visibility rules change for business and legal reasons, not engineering ones. I keep them out of code, versioned, reviewable and signed off by the people who own them.
A business case, success metrics and an operating model come first, built with CX, finance and operations. It is how a good idea becomes a funded roadmap.
I build working proofs of concept early so stakeholders react to something real. Scenarios are agreed with analysts and product owners before the build, not after.
Audit logging, human review of AI output, stage gates and risk tiering are designed in from the start. In regulated work, trust is a feature.
I paused an AI letter-generation project whose mandate was to recreate the existing process. It would not have made letters faster or better. Agreeing the foundations first was the right call.
Seven products from the Claims and Leave Management platform at Unum, then earlier work at Shaw Contract. Each is framed the way I would pitch it: the problem, what I owned, how it works, and what changed.
Product leadership · Digital self-service
Replacing email, phone and fax collection with one digital-first ecosystem.


Screens show example data.
Information needed to decide a claim was collected by email from employers and by phone and fax from claimants. It was slow, manual, hard to track, and created outbound calls to chase it.
I led discovery, current-state assessment, the business case and the solution design, then delivered in increments across personas, topics and product lines.
Product & technology · Digital intake
Claim filing that moved from an 18-minute phone call to a form customers complete any time.

Screens show example data.
Starting a claim meant an 18-minute phone call. Intake was also customized per employer, which does not scale. Accurate, complete data at intake is what lets a claim be processed at all.
Before
An 18-minute phone call to start a claim.
18-minute callPer-employer custom intake
After
Customers file their own claim online, with leave planning and their employer’s content built in.
24/7 filingLeave planningEmployer dynamic content
Hands-on in the design and build of the Employee Portal, including the claim intake form.
Product & technology · Employer self-service
The people who manage employees on leave get what they need in one place, without an email.


Screens show example data.
HR teams and managers need to know who on their team is out, when they are expected back, and what Unum needs from them to support their people. That used to arrive by email, hundreds of thousands of them.
Before
Emails to chase and answer, one case at a time.
Hundreds of thousands of emailsNo single view of who is out
After
One portal showing who is out, when they return, and what Unum needs, handled as digital tasks.
Who’s outExpected returnTasks for me
Hands-on in the design and build of many aspects of the Employer and Manager portals, as part of the same digital self-service program as the Employee Portal.
Technology leadership · Platform & AI-assisted build
One consistent answer to “what is happening with my claim?” across portals, agents, letters, email and IVR.




Screens show example data.
Every channel carried its own front-end logic to interpret raw case data. The same business rule, such as what “Approved” means on a reduced-schedule leave, was duplicated and drifted, so a claimant could hear different answers from different places.
I designed and built it with Claude Code, in partnership with Platform Engineering. I aligned business analysts and product owners on 29 claim-status scenarios before build.
Product & governance · Business-owned change
Let the business change claimant-facing wording and visibility, with an audit trail and the right sign-offs.


Screens show example data.
The rules decide claimant-facing wording and which documents each audience sees. They change for business and legal reasons, and a change needs an auditable trail. Burying them in code puts every change in an engineering queue.
I defined the product: who edits, who approves, and how a change is promoted. I also built the working editor with Claude Code.
Multi-level approvals for business and legal/compliance, with a link to the ticket in the legal team’s workflow tool. Assignees are tracked by department or role. The integration is designed as a swappable adapter, so a real one can replace the demo.
Product leadership · Conversational & agentic AI
Giving the phone channel its first self-service, live in six weeks, and building a platform we owned rather than a vendor demo.
The phone experience had no self-service options at all. Two things were true:
With Digital Tasks, because they are contained flows. We already know why we are asking: we need the information, so we identify the intent rather than relying on what the caller says they want. We know what success looks like and how to guide the caller to it. That let us go fast to prove the technology, then scale from there.
I owned the vendor evaluation and led all aspects of the Parloa implementation, doing much of the work directly and managing the team members who did the rest. I defined the business case, operating model, success metrics and adoption roadmap with engineering, data and operations. I then led the production agent hands-on for 16 months before transitioning it to a scrum team.
We chose it for speed and scale, and delivered the pilot in six weeks from signing the contract to production calls. It gave us:
The enterprise set a standard that conversational AI and contact center tools should be built on AWS. To align with it, the agentic IVR moved to Amazon Connect, Lex and Bedrock. I compared approaches and trade-offs, defined like-for-like requirements and tested the AWS solution, then supported the move and the engineers building it. Because we owned the knowledge of how the agent worked, we were moving something we understood.
Product & technology · Contact center
Putting the right information on the agent’s screen, and guiding the most important call so it is done right the first time.
Contact center agents work in a complex, high-stress environment. Taking a new claim is the highest-stakes call: the data has to be accurate and complete for the claim to be processed at all, and it has to be captured quickly. New agents join through a “street to seat” hiring model, so the tools have to guide as well as record.
I supported the development of Unum’s Amazon Connect instance, the contact center platform that the IVR sits in front of. That included a custom agent portal and custom call dispositioning. I designed and guided the requirements for several agent tools, including the guided intake solution.
A $1B global commercial flooring business with no digital product organization. I built one, and the platform that came with it.
Product & technology leadership · 0→1 platform
Shaw Contract’s first digital product and customer experience, live in 10 months from funding.




A $1B global business serving 14 markets had no digital product organization and no platform to build on. Customers could not buy or order samples online, and support did not scale with demand.
I built and led the organization and the case for it. I was heavily involved in stack selection and architecture, and led the build-vs-buy and vendor decisions.
Product leadership · Digital transformation of a flagship program
A beloved annual program, rebuilt as an online experience when the pandemic made the old one impossible.






The awards had run successfully for many years. Every year, hundreds of projects were submitted by the world’s leading design firms, from NFL stadiums and global headquarters to five-star hotels, retail giants, universities, airports and world-class healthcare facilities. Importantly, flooring was not the criterion. It was Shaw Contract celebrating good design, not just its own product.
The program was excellent. The process was not.
Before
Emailed entries, hand-built foam core boards, judges flown in for two days, results in print.
Manual layoutIn-person onlyPrint and blog reach
After
Enter online, judge in a secure portal, finalize in virtual sessions, and open the winners to a public vote.
Self-serve entryRemote judgingPeople’s Choice
We had just relaunched the site and wanted projects to be a central element of it. I led the product decision to build that function out further and make the awards its first major use, taking the whole program from entry to winners online.
The program kept its spirit, celebrating design for its own sake, and became bigger than it could have been in a ballroom.
Product leadership · 0→1
The email thread is the worst product in B2B. We made the project itself the product.


I thought the challenge in commercial flooring was helping customers choose the right product. It was coordinating people. At our annual Brand Meeting, more than 400 account managers from around the world were crouched by power outlets and standing outside keynotes, emailing screenshots, reading specifications over the phone and forwarding PDFs, because their customers back home were waiting.
We had built a product catalog, not a customer experience.
Before Boards
Screenshot, email, call, forward, repeat.
No shareable linkNo sample trackingNo Salesforce sync
After Boards
One link, everything inside: products, videos, coordinating Benjamin Moore paint, samples and quoting.
No loginSalesforce connectedNo email required
With a colleague, I spent weeks travelling the country with designers, flooring contractors, architects, facility managers, healthcare systems, schools, hospitality groups and corporate customers. The industries differed, but every conversation sounded the same: they were all coordinating a project through email. Customers were not struggling to buy flooring. They were struggling to move a project forward.
I conceived Boards as a 0→1 product and led it from discovery through launch and iteration.
The lesson: customers don’t wake up wishing for a better website. They are trying to complete a job. Design around that.
As the first use case on Unum’s AI governance platform, I led governance with the compliance team and enterprise partners. That set up risk tiering, controls, stage-gate check-ins and enterprise visibility for the AI use cases that followed.
Apr 2021 – Present
Principal Business Analyst, Enterprise Business Architecture & Portfolio Strategy
Partner to AVPs, Heads of Delivery, and IT Vice Presidents across Claims and Leave Management, turning strategy into funded roadmaps and delivery-ready work for platforms supporting 25,000+ new claims monthly and 65,000+ active digital users.
→ 99% accuracy on new claim intake calls (accurate and complete data capture needed to process a claim)
→ Parloa pilot: 25% of opted-in callers completed their task without an agent · 30% lower handle time (call + after-call work) vs. pre-pilot baseline
→ 1M+ transactions in 2026 YTD · Information received ~2.5 days faster · Fewer outbound calls · Digital intake 20% → 80% · CX 4.4 employee / 4.5 employer
Apr 2016 – Apr 2021
Digital Marketing Manager, Enterprise Digital Transformation
Apr 2018 – Apr 2021
Built Shaw Contract’s first digital product and customer experience organization for a $1B global business (14 markets, 100,000+ monthly users), launching the initial platform within 10 months of funding.
→ 350% more AI-enabled support capacity with 20% lower handle time · 70% more sample orders · ~50% lower annual operating costs
Workplace Marketing Manager, Product Strategy & Customer Acquisition
Apr 2016 – Apr 2018
Feb 2013 – Apr 2016
Account Executive, Digital Strategy Consulting
Jun 2012 – Feb 2013
Junior Account Executive (Chicago-based agency, Chattanooga office; held during college)
Apr 2010 – Jun 2012
Research Associate (held during college)