The Dashboard That Broke Everything

Sarah Chen sat in the parking lot of ClassicMotors.io headquarters, staring at a pristine 1967 Shelby GT500 in the visitor spot next to her.

She'd driven from Detroit in her 1990 Mustang GT - bright red, Weld Rodlite wheels, Street legal drag slicks on the back, windows down the whole way. The sensible thing would have been to fly. But this wasn't a sensible day. This was the day she left behind fifteen years at General Motors. Left behind the VP of Analytics title. Left behind stock options that were about to vest.

For this.

A startup in a converted warehouse in San Jose with a Shelby as office decoration.

But that Shelby - God, that Shelby - was exactly why she was here.

* * *

Six Weeks Earlier

Jack Torres had called her out of the blue. "Sarah Chen? The Sarah Chen who built GM's manufacturing analytics platform?"

"That's me," Sarah said, suspicious. Recruiters called weekly. Most wanted her to build ad-tech dashboards or optimize e-commerce funnels. Hard pass.

"I'm Jack Torres. I run ClassicMotors.io. We're an online auction platform for classic cars."

Sarah perked up. "Like Fetch a Flatbed?"

"Similar concept, different soul," Jack said. "Fetch a Flatbed is great at what they do - high-volume auctions, clean interface, strong community. But here's what we're building: we believe classic cars aren't just assets. They're time machines."

Sarah smiled. "Go on."

"I own a 1981 Porsche 911," Jack continued. "SC model, Tin Metallic in color – a smokey shade of silver, original everything. When I slide into that driver's seat, I'm not in 2024 anymore. I'm in 1981. I can smell the leather, feel the mechanical steering, hear that flat-six sing. It transports me back to a simpler time. That's not a transaction - that's an emotional experience."

"I get that," Sarah said. And she did. She had purchased her 1990 Foxbody Mustang GT back in high school. In fact, she'd just driven it from Detroit to San Jose. That car had earned its place in her story. A few years back, the head gaskets started leaking - oil pooling where it shouldn't, the 5.0 losing compression. Most people would've taken it to a shop. Sarah tore the motor down herself. Spent three weekends in her Detroit garage in July, humidity so thick the wrenches were slippery, bloody knuckles from fighting bolts, grease under her fingernails for a month. But the head gaskets were the excuse she'd been waiting for. Aluminum heads. A lopey cam that made the car sound like it was breathing. The idle at a stoplight now had a heartbeat - a low, uneven rumble that made people in the next lane look over. She'd turned a tired motor into something alive. Every bolt she'd touched, every gasket she'd seated, every knuckle she'd skinned had deepened something she couldn't quite name. It wasn't just her car anymore. It was proof that the boring, unglamorous work - the work nobody sees - is what turns something ordinary into something extraordinary. That car was a time machine too.

"Right?" Jack said, energized. "That's what we're building. Fetch a Flatbed treats cars like commodities - list it, bid on it, move on. We want to help people find their time machine. The car that takes them back to their first date, their first road trip, the car their dad drove. We want buyers to understand the story behind every car. And we want sellers to feel like they're passing on something precious, not just dumping inventory."

"So how does analytics fit into this vision?" Sarah asked.

"That's the problem," Jack admitted. "We've been operating on gut feel and passion. I love cars. Our whole team loves cars. But we're burning through cash, growth is slowing, and I have no idea which levers to pull. My board wants data. I need someone who can bring analytics discipline without killing the soul of what we're building."

Sarah felt the pull. A mission-driven company. A founder who understood emotion and craft. And classic cars.

"Why me?" she asked.

"Because you built GM's manufacturing analytics platform. You understand physical products with soul. You know how to balance craft and data. And "Jack paused….."I looked you up. You still own your high school Mustang. You get it."

Sarah laughed. "You did your homework."

"I need someone who loves cars and loves data. That's you."

Three interviews later, Sarah accepted the offer. Head of Analytics at ClassicMotors.io. Lower pay than GM. Startup equity that might be worthless. But the mission felt right.

And now here she was, sitting in the parking lot next to a Shelby, about to walk into her first day.

* * *

Day One

Jack met her at the door, grinning. "You made it! Welcome to the madhouse."

He gave her the tour. The warehouse had exposed brick, vintage racing posters, and a rotating showcase of cars for auction. Today: the Shelby GT500, a 1972 Ferrari Daytona, and a mint 1985 Toyota Land Cruiser FJ60.

"We rotate cars through the office every week," Jack explained. "Keeps the team inspired. Reminds us why we're here."

Sarah smiled. This place had soul.

Then Jack introduced her to the data team.

Marcus (Lead Data Engineer), Jin (Senior Analyst), and two junior analysts who looked exhausted.

"Team, this is Sarah Chen, our new Head of Analytics. Sarah, this is the team that's been keeping the lights on."

Sarah shook hands. Marcus looked wary. Jin looked hopeful. The junior analysts looked like they hadn't slept in days.

"Show her the dashboards," Jack said.

Marcus pulled up a screen. "We have forty-seven dashboards."

Sarah blinked. "Forty-seven?"

"Forty-seven," Marcus confirmed. "Product asked for twelve. Marketing asked for eight. Finance asked for six. Sales wanted nine. Operations needed five. And then people kept asking for custom variations."

"How many people use them?" Sarah asked.

Marcus pulled up usage data. "About twelve percent of stakeholders log in regularly. Three dashboards get heavy use. The rest... barely touched."

Sarah did the math. They'd built 47 dashboards. Only 3 were used heavily. That meant 44 dashboards - 94% of their output - were gathering digital dust.

"So we're running a factory where ninety-four percent of our production goes straight to the landfill," Sarah said.

Marcus winced. "I mean... I guess that's one way to put it."

"That's the only way to put it," Sarah said. "This is a disaster."

Jin spoke up. "To be fair, we were just trying to help. People ask for dashboards, we build them. What else are we supposed to do?"

"Say no," Sarah said simply. "Or at least ask why they need it and what they'll do with it."

"But they're stakeholders," one of the junior analysts protested. "We can't just say no."

"You can and you should," Sarah said. "Every dashboard you build costs time, money, and attention. If nobody uses it, you've wasted all three."

She turned to Jack. "How big is the data team?"

"Five people, including you," Jack said.

"And how much time do they spend building new dashboards versus maintaining existing ones?"

Marcus sighed. "Eighty-five percent building new ones. Fifteen percent maintenance and firefighting."

"So you're constantly building and never improving," Sarah said. "And the dashboards you built six months ago are probably broken or outdated because nobody maintains them."

"Pretty much," Jin admitted.

Sarah pulled out her laptop. "Show me the three dashboards people actually use."

Marcus pulled them up:

Daily Revenue Dashboard - Sales team checked it every morning

Auction Performance Dashboard - Product team used it to optimize listings

Seller Engagement Dashboard - Marketing used it to target high-value sellers

"These are good," Sarah said. "Clean, focused, actionable. Why can't the other forty-four be like this?"

"Because people keep asking for custom stuff," Marcus said. "And we keep saying yes."

Sarah closed her laptop. "Okay. Here's what we're doing. Over the next two weeks, we're auditing every single dashboard. We're going to ask three questions: Who uses this? How often? What decisions does it drive? If we can't get good answers, we kill it."

The team looked stunned.

"Kill it?" Jin said. "Just... delete it?"

"Yep. We're going to take this factory from ninety-four percent waste to zero waste. We only build things people use. We only maintain things that drive decisions. Everything else goes."

Marcus raised his hand. "What if people get mad?"

"Let them," Sarah said. "I'd rather have three dashboards that people love than forty-seven dashboards that people ignore. Wouldn't you?"

The team exchanged glances. Slowly, they nodded.

* * *

The Audit

Over the next two weeks, Sarah and the team went through every dashboard.

They tracked usage logs. They interviewed stakeholders. They asked the brutal questions:

• When did you last look at this?
• What decision did you make because of it?
• If this dashboard disappeared tomorrow, would you notice?

The results were damning.

Dashboard #4: "Weekly Seller Funnel Analysis" - Requested by: Marketing VP (who left the company six months ago) - Last accessed: 87 days ago - Decision impact: None - Verdict: KILL IT

Dashboard #18: "Bid Pattern Heatmap" - Requested by: Product Manager (thought it would be "interesting") - Last accessed: Never (not once since launch) - Decision impact: Zero - Verdict: KILL IT

Dashboard #31: "Regional Performance Deep Dive" - Requested by: Sales (wanted to see performance by state) - Last accessed: 12 days ago (once) - Decision impact: "It confirmed what we already knew" - Verdict: KILL IT

By the end of week two, Sarah had a list:

• 3 dashboards with heavy daily use → KEEP
• 5 dashboards with weekly use and clear decision impact → KEEP
• 39 dashboards with minimal use or no impact → KILL

She called an all-hands meeting.

* * *

The Reckoning

Jack stood in front of the company with Sarah beside him.

"Team, we have a problem," Jack began. "We've been treating data like a vending machine. Anyone can request a dashboard, and the data team builds it. No questions asked. No strategy. Just build, build, build."

He pulled up a slide showing 47 dashboard thumbnails.

"We built forty-seven dashboards. Twelve percent of you use them regularly. Three dashboards get heavy use. The rest are abandoned."

Murmurs rippled through the room.

"Here's the reality," Jack continued. "Our data team spends eighty-five percent of their time building new dashboards and fifteen percent maintaining them. That means the dashboards we built six months ago are broken, outdated, or wrong. And nobody notices because nobody uses them."

Sarah stepped forward. "Starting today, we're changing how we work. We're killing thirty-nine dashboards. We're keeping eight. And going forward, every new dashboard request gets three questions: Who will use this daily? What decision will it drive? What happens if we don't build it?"

A hand shot up. "What if I need a dashboard you killed?"

"Then you tell us why you need it and what you'll do with it," Sarah said. "If it's a good reason, we'll rebuild it. But we're not building things people might use someday. We build things people will use today."

Another hand. "What if my request gets rejected?"

"Then we've saved you from a dashboard you wouldn't have used," Sarah said. "Trust me, you're better off."

Jack wrapped up. "This isn't about being mean. It's about being smart. We're a startup. We have limited time, limited money, limited attention. We can't afford to build things nobody uses. We build what matters. We kill the rest."

The meeting ended.

* * *

The Aftermath

Sarah and Marcus spent the next day shutting down 39 dashboards.

It felt liberating.

Every deleted dashboard freed up server capacity, reduced maintenance burden, and cleared mental clutter.

By the end of the week, the data team had eight dashboards. All eight had daily active users. All eight drove real decisions.

Sarah pulled up the team's calendar. It had changed dramatically:

• Before: 85% building new dashboards, 15% maintenance
• After: 30% building, 70% improving what existed

"How does it feel?" Sarah asked the team.

Jin grinned. "Like we can finally breathe."

Marcus nodded. "I didn't realize how much stress those dead dashboards were causing. Now we can actually make the good ones great."

Sarah smiled. "That's the goal. Less waste. More value. Build things people love."

* * *

Three Weeks Later

Sarah sat in Jack's office for her first one-on-one.

"How's it going?" Jack asked.

"Good," Sarah said. "We killed the waste. Now we need to fix the strategy."

"What do you mean?"

Sarah pulled up the three most-used dashboards. "These are good. But they're all backwards looking. Revenue yesterday. Auctions last week. Seller activity last month. We're driving by looking in the rearview mirror."

"So, what do we need?" Jack asked.

"Forward-looking metrics," Sarah said. "What predicts success? What are the leading indicators? What should we focus on to grow?"

Jack leaned back. "That sounds harder."

"It is," Sarah admitted. "But that's where the magic happens. Anyone can report what happened. Great analytics teams predict what's about to happen and tell you what to do about it."

Jack grinned. "That's why I hired you."

"Yep," Sarah said. "But first, we have another problem."

"What now?"

Sarah pulled up a different dashboard - one they'd kept. It showed total registered users: 1,047,893.

"See that number?" Sarah said.

"Yeah. Over a million users! That's great."

"That's the problem," Sarah said. "That number is killing us."

Jack looked confused. "How is growth a problem?"

Sarah smiled. "Let me show you."

And that conversation would change everything.

Sarah had seen this before. At General Motors, she'd stood on a catwalk above the manufacturing floor, watching production flow like a river. Every bottleneck was visible. Every problem was measurable. Every inefficiency was obvious.

She'd go back to her analytics desk and feel blind. The work was invisible. The problems were hidden. The waste was unmeasurable.

Until now. Now, with 47 dashboards nobody used, the waste was finally visible.

She just had to make everyone else see it too.