Graphics Department Rebuild

This project was bigger than fixing a creative workflow.

It was about taking a department that had become reactive, unclear, and financially unhealthy, then rebuilding it into something the team could understand, the business could trust, and the customer could count on for accurate pricing and consistent quality.

I had history with the work already. Early in my career, I helped bring vehicle graphics production in-house, built customer renderings and presentations, and turned those concepts into real vinyl packages for ambulances and fleet vehicles. Years later, after the department had grown under other leaders and then lost them, I was asked to step in and manage it.

I did not want the job. I already had enough on my plate.

But, I took it anyway, because the team needed help and the department clearly needed a rebuild.

The Problem

What I found was a team that was very good at putting out fires.

That sounds useful until it becomes the whole culture.

The department had gotten good at reacting to whatever was directly in front of it, but it was not structured well enough to improve, catch up with production, or think beyond the next urgent problem. People were busy, but they did not always understand how work came into the department, what happened after they handed it off, or why certain decisions were being made.

That lack of clarity created the usual noise. People blamed individuals. I heard plenty of comments about who was failing, who should be let go, and who was not good enough.

To me, that was missing the point.

The people were not the main problem. The system was. In some cases, the department had hired people into roles without clearly defining what the job required. In other cases, the team held people accountable for outcomes without enough clarity on process, purpose, or handoff.

There was also a bigger issue underneath all of it: the department was not making money.

The Groundwork

I started the way I usually do: I dug in.

I needed to understand how the work actually moved, how materials were being used, where process broke down, how jobs were handed from Graphics to Installation, and what the department was really costing the business.

One of the biggest questions was simple: are we making money?

The answer was no. Not even close.

So the groundwork became part workflow rebuild and part business reality check.

I started by inventorying the warehouse materials so we had a clear picture of what we had on the shelf, what was expired, what needed to be stocked, and how much money was sitting there. Then I worked through current material costs and built a way to understand cost per inch for the materials we used most often.

From there, I needed to understand the jobs themselves.

What I found was that we were really producing about four tiers of job complexity. So I pulled a sample of jobs from each tier and did a cost study using the cut files we already had saved. That let me see how much material actually passed through the printer, how much laminate was required, and what the real material cost per job looked like, including waste.

Then I averaged the jobs by tier, applied markup, and started building a more honest pricing structure.

Labor was the next challenge. Graphics would print and cut the jobs, then hand them off to the install team. If something was damaged during installation, Graphics often took the blame. That was not always true, but it revealed a bigger need: we had to understand labor cost clearly across both Graphics and Installation so we could price the work correctly and stop guessing.

Rebuilding the Graphics Department

I rebuilt the department around clarity, process, pricing, and people.

That meant redesigning the offering itself, not just cleaning up the workflow. I built a tiered pricing structure based on actual material cost, design labor, production labor, installation labor, and business-standard markup. Then I presented the findings and the proposed fix to leadership and got the green light to move forward.

I also found another visible problem: the presentation templates the team was sending to customers looked unprofessional and did not communicate clearly enough what the finished unit would actually look like. The person creating them was trying, but the system was not helping her succeed.

So instead of just taking the work away from her, I rebuilt the template. I listened to customers, listened to Sales, applied my own design judgment, and created a new presentation system with stronger branding, clearer communication, and version control the team could actually follow. Then I rolled it out and trained everyone on how to use it.

That improved more than the visuals. Better templates reduced confusion, improved consistency, and helped the team present the work with more confidence.

Once the pricing structure was approved, the next step was rollout.

I set the date for the new pricing to take effect, trained the purchasing team on what to buy and stock, helped define when materials should be issued, and trained the CPQ team on how Sales should quote the new tiers and prepare customers for the increase in cost.

That part could have gone badly. The pricing jump was significant, and we were not sure how customers or Sales would take it.

Rolling Out the New Structure

In reality, it went smoothly. Sales bought in. Customers understood. And the department started doing something it had not been doing nearly well enough before: making money.

At the same time, I worked on the team itself. I developed existing people, hired two more, let one go, and eventually hired a supervisor who helped continue the department’s growth. Later, I promoted that supervisor into the manager role and handed the team over so it could have more focused leadership than I could realistically give it long term.

That mattered too. The goal was never to make myself the permanent center of the department. The goal was to stabilize it, strengthen it, and hand it off in better shape than I found it.

Tools Used

I used a mix of design, operational, and documentation tools to rebuild this department. The tools mattered, but only because they helped me improve the customer-facing work, understand the real cost structure, and build processes the team could actually follow.

Tool	Purpose
Adobe Illustrator	For rebuilding the customer presentation templates, improving visual quality, and training the team on the new system.
Google Sheets	For building the job cost calculator, tracking material cost per tier, managing inventory, and establishing a real pricing structure.
CPQ Tools / ERP	For training Sales on how to quote the new pricing tiers and connecting the pricing structure to the broader business system.
Google Docs	For writing SOPs, process documentation, and creating the reference materials the team could actually follow.
ChatGPT & Claude	For drafting documentation, refining SOPs, and pressure-testing process logic as the rebuild took shape.

The Result

The result was a healthier department.

The team had more clarity on what it was doing and why. Pricing, inventory, workflow, handoff, and customer-facing presentation all had better structure. Sales had a clearer way to quote the work, purchasing had a clearer way to support it, and leadership had a department that was no longer quietly losing money.

Just as important, the rebuild changed the story around the team.

Instead of assuming the people were the problem, we built a better system around them. That made it easier to see where guidance was needed, where roles needed to change, and where the department could actually grow.

For the customers ordering this work, it meant clearer expectations going in, pricing that reflected what the job actually required, and a finished product that matched what they had been shown before the work started.

A rebuild like this should do more than reduce friction. It should make the function healthier, more teachable, and more sustainable.

What This Project Proved

This project proved that leadership is not just about stepping in and judging what is broken.

It is about understanding why it is broken.

A lot of teams get criticized for poor output when the real problem is weak structure, unclear expectations, bad pricing, or a process that never made sense in the first place. My job here was not to blame the team. It was to understand the system, fix the parts that were failing, hire where we needed strength, and build it to a point where someone else could carry it forward.

That is the kind of work I like most. Dive in. Figure out what is really happening. Fix it piece by piece. Then design it well enough that it can survive without you.