Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Building a Cross-Functional Dashboard
Transcript
- Lucas: So there's this story I came across — a marketing analyst at a retail tech company, about eight hundred employees. She was three years into her role, solid performer, but stuck at the same level. No obvious path to senior manager. Luna: That's a pretty common ceiling, right? You're doing good work, but nobody's handing you a promotion just for showing up. Lucas: Exactly. And what she did was not wait for a job opening or a reorg. She looked at a problem everyone complained about but nobody owned: the company had no single view of how marketing spend translated into product usage. Sales used Salesforce, product used Mixpanel, marketing used HubSpot — and the data never talked to each other. Luna: Oh, I've lived that nightmare. Quarterly reviews where three teams bring three different numbers for the same metric. Lucas: Right. So she built a lightweight dashboard that pulled key fields from each system into one Google Sheets dashboard at first — not even a real BI tool. She spent maybe ten hours over two weekends. Luna: Wait — Google Sheets? That's not exactly enterprise-grade. Lucas: That's actually the smartest part. She didn't ask for budget or permission. She prototyped with free tools. The goal wasn't to build the perfect system — it was to prove the concept. She called it 'the marketing to product conversion view' and shared it with her manager as a 'here's something I've been tinkering with, curious if you find it useful.' Luna: Low risk, high potential upside. If her manager ignored it, she's out a weekend. If it sticks, she's suddenly the person who solved a cross-team pain point. Lucas: And it stuck. Her manager shared it with the VP of product, who shared it with the CMO. Within three weeks, the CMO was pulling it up before weekly leadership meetings. The dashboard wasn't fancy — it just answered a question no one else had answered: 'Of the leads marketing generates, how many actually activate in the product within thirty days?' Luna: That's the kind of visibility that changes a career. She went from one person's manager seeing her work to three executives seeing it every single week. Lucas: Exactly. And here's the key detail: she didn't just hand them a tool. She also wrote a one-page memo explaining the methodology, the data sources, and the limitations — things like 'this doesn't include organic traffic because we can't track it yet.' That built credibility. She wasn't overselling. Luna: So she combined a technical output with clear communication about what it can and can't do. That's a promotable combination. Lucas: Six months later, she was promoted to senior manager of marketing analytics. The company created a new role for her because they realized they needed someone to own cross-functional data strategy. She didn't just build a dashboard — she defined a new function. Luna: I think the lesson here isn't 'build a dashboard and get promoted.' It's more specific: she found a friction point that was costing executives time and mental energy — the weekly reconciliation of different data sources — and she removed it. That's a classic leverage point. Lucas: Yeah, the time-saving angle is huge. Executives hate wasted time. If you can save a VP thirty minutes a week on something tedious, you've created real perceived value. And that perceived value translates into visibility. Luna: But not every dashboard project leads to a promotion. I've seen people spend months building elaborate Tableau dashboards that nobody asked for and nobody uses. What made this one different? Lucas: Two things. First, she validated the need before building. She'd heard sales and product complain about data silos in meetings for months. She knew the pain was real. Second, she started tiny — a spreadsheet, not a data warehouse. That kept her investment low and made it easy to kill if it didn't work. Luna: So the lesson is: start with a prototype that solves a real, expressed frustration, and let the stakeholders pull you into a bigger role. Lucas: Precisely. And there's a strategic decision she made that I think a lot of people miss: she targeted the C-suite's problem, not just her team's. The marketing team might have been fine with their own data — but the CMO needed to see how marketing connected to retention. She solved an executive problem from an individual contributor position. Luna: That's a smart political move, too. By solving a problem for the people above your manager, you create a sponsor who has a stake in your success. Lucas: And she handled that carefully. She didn't go around her manager — she looped her manager in at every step. Her manager looked good for having a team member who could do this. So when the promotion came, the manager was an ally, not someone who felt bypassed. Luna: That's a delicate balance. How do you get executive visibility without making your direct boss feel threatened? Lucas: You frame it as a gift to your manager first. She told her manager, 'I built this to make your reporting easier, and I think it could help the VP too — would you be comfortable if I shared it?' That gives the manager control and credit. It's a small language shift that makes a huge difference. Luna: I want to circle back to the promotable skills here. It's not just about data. She had to understand the business context, map stakeholders, communicate clearly, and manage upward. Those are senior-level competencies. Lucas: Exactly right. The dashboard was the vehicle, but the skills she demonstrated are what got her the title. Systems thinking — she saw how marketing, sales, and product interacted. Stakeholder empathy — she knew what frustrated each group. And initiative — she didn't wait for someone to assign it. Luna: If someone's listening and thinking, 'I could do something like this,' what's the first step they should take this week? Lucas: Identify one question that comes up in every cross-team meeting that nobody can answer quickly. Write it down. Then ask yourself: can I answer that with data I already have access to? If the answer is yes, spend one afternoon building a rough version. Don't worry about polish — worry about whether it answers the question. Luna: And share it with your manager as a 'quick experiment' — exactly like she did. Low pressure, high curiosity. Lucas: Right. And if the question is too complex to answer with existing data, that's actually useful information too. You can write a one-pager outlining what data you'd need and what it would enable. That still shows initiative and strategic thinking. Luna: I think a lot of people underestimate the power of just making something visible. If you build a tool that five people use, that's fine. If you build a tool that the C-suite uses once a week, that's a promotion. Lucas: And that's exactly what happened here. She went from being a good analyst to being the person who made leadership smarter. That's a hard thing to quantify, but it's what got her the senior manager title. Luna: You know, this kind of concrete career story is exactly why we do this show. If it's helped you think differently about your own situation, we'd love it if you considered supporting the show. It keeps us ad-free and focused on stories like this one. You can do that at buy me a coffee dot com slash fexingo. Lucas: Yeah, that kind of support genuinely lets us keep diving into real, specific cases instead of generic advice. And we've got more of those coming. Luna: Before we wrap, I want to ask you about one risk I see with this approach. What if you build a dashboard and it goes nowhere? Does that hurt your career? Lucas: It's only a risk if you invest months and overpromise. But a weekend prototype that doesn't get traction? That's just learning. You still learned something about the business, about data availability, about stakeholder priorities. And you can have a conversation with your manager: 'I tried this, it didn't stick, here's what I learned.' That still shows initiative. Luna: So the downside is minimal if you keep it small and transparent. Lucas: Exactly. The real risk is doing nothing and waiting for someone else to notice you. That's a much worse bet.