• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

What’s up everyone, today we have the pleasure of chatting with Jenna Kellner, VP Marketing at Workleap & ShareGate.

Summary:  Jenna is a VP of marketing that can talk about the weeds of messy systems, uncertain decisions, and personal growth. You can’t hide from it, every company accumulates tech debt as teams rush to hit revenue targets. She frames tech debt as a leadership responsibility and urges executives to reinvest in core systems when patchwork begins to outweigh building. If leadership doesn’t get it, the best way to prioritize it is to shape it as an opportunity cost and lost leverage that will drain revenue the longer we wait. In the face of AI uncertainty, she argues that judgment compounds faster than technical knowledge, and that the marketers who become indispensable blend business awareness, proximity to execution, and decisive action grounded in humility.

In this Episode…

• The Frankenstein Reality of Managing Tech Debt
• How to Build Confidence With AI Through Small Experiments
• How to Use Exit Planning and Cost Benefit Analysis for AI Tool Selection
• First Principles Matter More Than Tools
• Why Staying Close to Execution Improves Marketing Leadership
• How to Build Business Judgment in Technical Marketing Roles
• Why Confidence Without Humility is Dangerous

About Jenna

Jenna Kellner is Vice President of Marketing at Workleap & ShareGate and a revenue-focused marketing leader who has spent more than a decade building marketing teams and scaling companies. She brings experience across Enterprise, SMB, D2C, SaaS, two-sided marketplaces, venture studios, and other high-growth environments.

Her career spans senior leadership roles at Minerva, On Deck, RBCx, and Ownr, where she led marketing, growth, and revenue functions inside complex, evolving organizations. At RBCx, she served as Chief Growth Officer for Ampli and directed marketing and growth initiatives within a large financial institution setting. She has also co-founded communities such as GrowthToronto and Little Traders, reflecting her commitment to building networks and businesses in parallel.

Jenna operates with a strong sense of ownership and accountability, grounded in her belief that every challenge ultimately becomes her responsibility to solve. Recognized as a WXN Top 100 Women in Canada, she focuses on developing high-performing teams that connect strategy to execution and translate marketing into measurable revenue impact.

The Frankenstein Reality of Managing Tech Debt

How to Manage Marketing Tech Debt During Rapid Growth

You know it.. Most marketers are operating inside half-connected systems. No company has a pristine, perfectly synchronized tech stack. Even if they think they do, it doesn’t last. Growth creates pressure, and pressure produces shortcuts. 

Jenna has seen the same cycle in startups and enterprise environments. In the early days, teams build whatever gets the job done. They start in spreadsheets, layer on point solutions, wire tools together with lightweight integrations, and move fast because revenue matters more than architecture.

Those early decisions never disappear. They compound. Years later, larger organizations inherit layers of systems that were added at different stages of maturity. Tools do not scale in sync. One platform gets upgraded. Another stays frozen because a team depends on it. Reporting becomes an exercise in orchestration. Jenna recalls walking into an organization where a sales leader pulled her weekly report from eight separate tools. That routine consumed time, drained energy, and normalized operational friction.

“You have to Frankenstein your way through them to get the answers you need.”

That sentence captures the daily reality inside many marketing and revenue teams. Quarter-end reporting still happens. Board decks still go out. The numbers get assembled through exports, CSV files, manual joins, and late-night reconciliation. Leadership often tolerates the strain because revenue continues to land. But the cost isn’t super visible:

• Reporting cycles stretch longer each quarter.
• Forecast confidence erodes.
• Team morale dips as manual work expands.
• Strategic decisions rely on partial or inconsistent data.

So how do we get out of this mess? Jenna views this as a leadership obligation. Someone has to decide that cleaning house earns priority alongside pipeline generation. She describes working with a founder who paused other initiatives to repair core systems. The work moved slowly. It required budget discipline and uncomfortable trade-offs. It rebuilt trust in data and freed leaders from cobbled-together dashboards. She compares the stack to a house. Repairs never end, but neglect guarantees structural damage. Leaders choose whether maintenance becomes routine or deferred risk.

Key takeaway: Treat marketing and sales tech debt as a leadership responsibility, not an ops inconvenience. Schedule deliberate cleanup cycles, secure executive buy-in early, and protect time and budget to rebuild core systems before the drag on revenue, morale, and reporting compounds beyond control.

Back to the top ⬆️

Prioritizing RevOps Tech Debt Without Perfect ROI Models

Just get buy-in to fix all of our tech debt… myeah… sounds great. Good luck convincing your leadership team who’s off chasing the next AI tool they just read about on LinkedIn. Just assign a dollar figure to it, doesn’t have to be perfect, just guestimate it. Someone is building a report by hopping across eight tools, copying fields, reconciling numbers. You can measure the hours. You can attach a salary. You still miss the real cost.

Jenna takes a different approach. 

She’s not a fan of squeezing every system fix into an artificial ROI model. She focuses on the role RevOps plays in revenue creation. She says it directly:

“The job is to enable sales and marketing to find patterns, to hunt better, to run better campaigns and plays, to drive stronger revenue.”

When RevOps becomes a reporting service desk, capacity shrinks. The team spends its energy on maintenance rather than momentum. The opportunity cost compounds quietly. High leverage work stalls, including:

• Designing sharper segmentation models.
• Identifying conversion bottlenecks across funnel stages.
• Equipping sales with data driven plays that improve win rates.

You feel the drag in slower experiments and reactive decision making. Pipeline velocity flattens. Leadership wonders why growth feels harder than it should.

The urge to quantify every hour saved can trap teams in defensive mode. You start arguing over whether saving ten hours per week justifies a cleanup project. You try to forecast the dollar value of future pattern recognition. That debate rarely captures the structural risk of lagging systems. Jenna frames it as a leadership judgment call grounded in timing and context. If headwinds are rising, if competitors are shipping faster, if your team spends more time patching than building, the signal is strong enough.

She points to industries that invested early in overhauling core systems. Airlines that modernized their tech stack gained operational speed and reinvested that advantage year after year. Those that layered bandages carried growing friction into every initiative. The same dynamic shows up in marketing organizations. Technical debt slows experimentation. Slower experimentation reduces learning cycles. Reduced learning cycles weaken revenue velocity.

A practical way to prioritize tech debt without falling into spreadsheet gymnastics looks like this:

1. Define the revenue outcomes RevOps should influence over the next twelve months, such as pipeline velocity, win rate lift, or campaign iteration speed.
2. Map the maintenance load that currently consumes capacity, including manual reporting, field cleanup, and tool reconciliation.
3. Describe the growth constraints in operational terms, slower launches, delayed analysis, missed optimization windows.
4. Tie the tech debt reduction plan to readiness for the next revenue milestone, whether that is a funding round, new market expansion, or a step change in pipeline targets.

That structure keeps the discussion anchored in growth capacity rather than hourly accounting.

Key takeaway: Stop chasing perfect ROI math for every piece of tech debt. Reframe the discussion around opportunity cost and competitive positioning; show how reclaiming RevOps capacity enables faster insights, sharper sales plays, and sustained revenue advantage.

Back to the top ⬆️

Reasoning Through Broken Systems and Imperfect Data

We’ve already established that we all operate inside fractured systems. Attribution models disagree, CRM fields break, finance reports lag, and someone always questions the integrity of the dashboard five minutes before a board meeting. The temptation is to pause and wait for cleaner data. Jenna sees that instinct as a leadership trap. She believes leaders must decide anyway.

“Everything is unknowable. You just can’t possibly predict everything.”

She treats uncertainty as part of the job description. In a recent role, she stepped into an organization without the data connectivity she needed to make fast, confident recommendations. She gathered partial inputs, identified directional signals, and placed informed bets. She made her assumptions explicit. She told her team that the plan would evolve within months. She normalized course correction. That discipline builds momentum in environments where hesitation quietly erodes trust.

The more uncomfortable truth is that even clean systems produce subjective narratives. One operator analyzes a dataset and recommends expansion. Another reviews the same dataset, adds three columns, and argues for contraction. Interpretation shapes outcomes. Jenna responds by structuring decision making around clarity rather than certainty. She walks through four elements before committing to a path:

1. Define the exact data inputs being used.
2. List the assumptions those inputs require.
3. State the specific bet the team is making.
4. Schedule a defined moment to reassess.

She then asks a critical question. If an assumption proves inaccurate, what changes in the strategy and how quickly? That question exposes whether the decision hinges on a fragile premise or a durable one.

She also expects leaders to invite others into the reasoning. Executives often crave confidence. Teams crave direction. Transparency satisfies both. When leaders share the data, the gaps, and the logic behind a recommendation, they distribute ownership. People understand the constraints and the tradeoffs. They know when to expect revisions. The organization moves forward with shared awareness instead of silent doubt.

Directional data does not eliminate risk. It provides motion. Teams that document their logic, revisit their bets on a calendar, and revise in public develop institutional agility. Teams that wait for pristine infrastructure slowly drift into stagnation. Jenna prefers motion with clarity over delay disguised as rigor.

Key takeaway: Build a repeatable decision cadence when your data is incomplete. Write down the inputs you trust, document the assumptions you are making, define the bet in concrete terms, and schedule a review date before you execute. Share that reasoning openly with your team. Revisit the decision on time and adjust with discipline. That structure creates forward momentum while keeping your strategy adaptable.

Back to the top ⬆️

Leading Through AI Uncertainty

How High Performers Progress Anyway

High performers inside tech companies share a habit that feels almost boring on the surface. They assume the plan will change. They expect the market to shift. They build their work around that assumption instead of fighting it.

Jenna talks about tech as constant whiplash. Budgets move. Priorities rotate. Customer sentiment tilts quietly before anyone updates the slide deck. She sees her strongest operators preparing for that movement in advance. When they bring forward a plan, they lay out three elements in clear language:

1. The current state of customer behavior
2. Two or three plausible directions the market could take
3. The signals that would confirm each direction

They then state a recommendation with conviction. They accept that conviction may evolve as new data arrives. That mindset keeps them steady while everyone else reacts emotionally to the latest twist.

“It might happen fast, but it shouldn’t be a surprise.”

Jenna ties surprise directly to distance from the customer. High performers build a rhythm around customer proximity. They listen to calls. They read support tickets. They notice when prospects start using new words or raising different objections. They pay attention to usage data that drifts slightly before it drops sharply. When strategy changes, they have already sensed it. The shift feels like a continuation of a pattern they were tracking.

She also points to something more personal. Some people internalize volatility as instability. Others treat it as terrain. High performers see themselves as interpreters of motion. They carry a point of view into leadership conversations. They do not wait for a perfectly clean environment. They operate inside the mess and keep moving. That posture compounds over time because leadership trusts people who can see around corners.

If you want to build that muscle, structure your week around signals:

• Choose five leading indicators that reflect customer behavior, not vanity metrics.
• Review them every week and write down what changed and why.
• Map at least two future scenarios for every major initiative.
• State your recommended path and the evidence supporting it.
• Join one live customer conversation weekly, regardless of your title.

Those habits anchor you to reality while everything else moves.

Key takeaway: Build a personal operating system around signals and scenarios. Define the customer indicators that matter, review them weekly, and attach clear recommendations to observable trends. Treat change as expected input and position yourself as the person who interprets it early. Consistent signal monitoring paired with decisive scenario planning creates momentum even when the ground keeps shifting.

Back to the top ⬆️

How to Build Confidence With AI Through Small Experiments

Leaders stall when they treat ambiguity as a problem that must be solved before action begins. Many people approach AI this way. They believe they need to understand every mechanic, every use case, every edge case before they test anything. Jenna sees that instinct frequently, especially among high performers who built their careers on expertise and control. The desire to feel fully informed becomes a quiet barrier.

She believes growth requires a different posture. Professionals who advance accept incomplete information as a constant condition of leadership. They break intimidating systems into smaller moves and begin before they feel ready.

“You can never know everything before jumping in.”

That principle applies whether someone is an individual contributor, a team lead, or aiming for management. As scope increases, the need to release total control increases as well. Leadership demands comfort with ambiguity because clarity often arrives after action, not before it.

Jenna encourages teams to design small, contained experiments instead of waiting for full comprehension. That means choosing environments where mistakes carry limited consequences. A leader testing an AI summarization tool on internal documentation operates in a different risk zone than someone automating a revenue-critical customer journey. Assessing the blast radius matters.

A simple framework keeps momentum moving:

1. Write down what you do not understand about the tool.
2. Select a low-risk workflow where you can test it.
3. Define a narrow outcome you want to observe.
4. Run the test within a short window, then document what happened.
5. Share the result with your team.

That sequence builds confidence because it converts abstract anxiety into concrete data. Each small experiment reduces the psychological cost of being wrong. Each iteration increases fluency.

Jenna also challenges the common excuse around time. Leaders with multiple direct reports and cross-functional responsibilities rarely control large blocks of uninterrupted focus. Their calendars fill quickly. They context switch all day. Waiting for a perfect two-hour window to study a new system delays progress indefinitely. Leaders build capability in shorter cycles.

She encourages thirty-minute bursts of active learning. She encourages paired exploration, where one teammate screenshares and narrates their decisions while using a new tool. Observing live workflows accelerates pattern recognition. Reading documentation helps, but watching someone navigate friction in real time deepens understanding faster.

“What can you bang out in half an hour?”

That question reframes learning as incremental rather than monumental. Over weeks, those half-hour sessions compound. The muscle of acting under partial clarity strengthens.

Leadership magnifies ambiguity rather than reducing it. As responsibilities expand, decisions stack, priorities collide, and new technologies appear faster than anyone can fully digest them. Confidence forms through repeated cycles of action, reflection, and adjustment. Teams mirror what they see. When leaders test visibly and share outcomes candidly, psychological safety grows in practical ways.

Key takeaway: Build leadership confidence in AI by committing to weekly, low-risk experiments. Identify one narrow use case, run a contained test within five business days, document the outcome, and share it with your team. Protect short learning blocks on your calendar and use them for hands-on testing instead of passive reading. Invite a teammate to demonstrate their workflow so you can observe real decisions in motion. Repeat this cycle consistently.

Back to the top ⬆️

How to Use Exit Planning and Cost Benefit Analysis for AI Tool Selection

AI buying decisions feel heavier than they used to. Every vendor claims to redefine productivity. Every demo suggests you are one integration away from operational bliss. Jenna treats that atmosphere as background noise and returns to discipline.

When asked how she leads when certainty feels temporary, she grounds the conversation in first principles. She starts with the problem, not the platform. She wants a written articulation of the constraint in the system, described in language a non technical executive can understand. If a team cannot describe the friction clearly, she pauses the evaluation.

From there, she forces a cost benefit frame. She asks teams to quantify improvement thresholds before they see the demo. She often walks them through a simple structure:

1. Define the specific workflow or metric under pressure.
2. Estimate the current cost of that friction in hours, revenue, or error rate.
3. Set a minimum improvement threshold that justifies disruption.
4. Define the time horizon for evaluating performance.

She reminds leaders that tools do not need to be proven for five years to create value. They need to solve a material problem better than the status quo. She also warns that improvement without durability creates operational fatigue. If a tool delivers incremental gains but demands constant retraining and maintenance, the hidden cost surfaces later in morale and focus.

Her second discipline is expectation setting. She asks executives to agree, in advance, that the tool has a defined lifespan. She often frames it this way:

“Assume this works for the next twelve to eighteen months. Assume we will revisit it. Build with that in mind.”

That framing changes how teams architect workflows. They document integrations more carefully. They avoid embedding logic in obscure corners. They choose configurations that remain portable. Leaders feel steadier because the possibility of change sits in the open rather than lurking in the background.

The most pragmatic move in her process is exit planning before contract signature. She asks teams to model the departure path in concrete terms:

• Where does the data live, and how easily can it be exported in a usable format?
• Which workflows depend on proprietary logic or closed APIs?
• How many people will need retraining if the tool is replaced?
• What budget and time buffer should be reserved for migration?

This exercise surfaces tradeoffs early. Some tools are easy to adopt but deeply entangling over time. Others integrate cleanly and leave cleanly. When leaders see that difference on paper, they make calmer decisions. They treat vendors as modular components inside a broader system rather than as permanent infrastructure.

AI will continue to shift categories, pricing models, and capabilities. Jenna leads with the assumption that impermanence is standard. First principles, explicit tradeoffs, and documented exit paths create stability inside movement.

Key takeaway: Before purchasing any AI tool, write a one page decision brief that defines the exact problem, quantifies the current cost, sets a minimum improvement threshold, and specifies a twelve to eighteen month evaluation window. Add a documented exit plan that covers data portability, workflow dependencies, retraining effort, and migration budget. Share this document with stakeholders before signing. This discipline creates alignment, reduces emotional overreaction to vendor hype, and keeps your stack modular instead of fragile.

Back to the top ⬆️

First Principles Matter More Than Tools

Constraints create clarity. Jenna treats that line as an operating rule, not a slogan. She believes every serious marketing decision should begin inside a defined boundary. Time, budget, team size, revenue targets, scope. Each constraint narrows the field and forces sharper thinking.

She has seen what happens without them. Teams spend months evaluating tools. Meetings multiply. Spreadsheets grow heavier. Nobody owns the call. Motion feels productive, but progress stalls. Jenna describes a different cadence:

“Operate everything you do within a constraint. Whether that be time, money, scale, team size, targets. Those boundaries create the box you operate in.”

That box matters. When the boundary is clear, tradeoffs surface quickly. You stop asking what is possible in theory and start asking what is possible now. You define the constraint. You do your due diligence inside it. You assign one accountable owner. You set a decision date. Then you move. Those steps feel uncomfortable because they remove the safety net of endless analysis, but they build muscle.

Her second principle flows from the first. Judgment beats optimization. Marketing culture often celebrates optimization because it feels rigorous. Dashboards expand. Tests stack up. Small gains accumulate. Jenna respects optimization, but she values decisive judgment more. She believes you can optimize for months and still avoid committing to a direction. A clear call, made under constraint, produces momentum. Momentum produces data. Data sharpens the next call.

Leadership complicates this as scope grows. Jenna speaks openly about the tension between staying close to the work and investing in executive relationships and team development. She chooses proximity. She wants to understand the tools her team uses, the friction in the workflows, the bottlenecks that slow execution. That proximity informs judgment. Leaders who understand the terrain set smarter constraints and make faster calls. Distance may create abstraction. Proximity creates conviction.

Key takeaway: Before your next major decision, write down three explicit constraints: a fixed deadline, a capped budget, and a clear owner. Limit research to a defined window. Require a recommendation that fits inside those boundaries. Make the decision on schedule and review impact after 30 days. Repeating this cycle builds judgment, shortens decision loops, and prevents your team from hiding behind endless optimization.

Back to the top ⬆️

Developing Judgment and Staying Close to the Work as a Marketing Leader

Why Staying Close to Execution Improves Marketing Leadership

Leaders who drift too far from execution lose judgment first. They lose the texture of the work, the friction inside campaigns, the tension in a sales narrative that almost lands but does not. The dashboard still loads. The forecast still updates. However, the instinct for what will actually move revenue starts to dull.

When asked what leaders give up when they step too far away, Jenna points to craft. She wants to learn from leaders who know what they are talking about. She holds herself to that same expectation.

“I want to be that person that isn’t so out of touch with the weeds of marketing, sales, revenue.”

For her, staying close to the work means maintaining the ability to answer real questions. She wants to defend a strategy in an executive meeting because she understands how it was built. She wants to coach from empathy because she has felt the constraints herself. She wants to carry accountability for results with full context, not surface awareness. That requires proximity. It requires reading the draft, listening to the call, pressure testing the positioning.

That proximity has a rhythm. Jenna talks about leaning in and leaning out. Leaning in might look like:

• Jumping on a screen share to rewrite a section together.
• Working through a stuck campaign in real time.
• Asking detailed questions about why a metric moved.

Leaning out means:

• Letting a director make the final call.
• Giving space for experimentation.
• Allowing someone to carry the weight of ownership.

The distinction lives in intent. When involvement feels like partnership, energy increases. When it feels like surveillance, morale drops. Jenna aims for coworking. She describes moments where she and a teammate “mesh our brains and our different styles,” and the output improves because two perspectives sharpen each other. Those sessions build respect because the leader contributes substance, not commentary from a distance.

There is also a hiring philosophy behind this. Jenna hires people who stretch her thinking. She looks for different cognitive strengths, different instincts, different ways of solving problems. That creates a team where learning moves in both directions. A leader who understands the details can challenge assumptions and defend decisions. A team that feels trusted can run with conviction. The culture benefits from both forces operating at the same time.

The cost of detachment is subtle but cumulative. Leaders who operate several layers above execution start speaking in abstractions. Feedback turns vague. Coaching turns generic. Teams sense the gap. Staying close preserves clarity. It sharpens strategic calls because those calls rest on lived context. It builds credibility because the leader can roll up their sleeves when needed and then step back without insecurity.

Key takeaway: Block one recurring session each week to engage directly in live execution, whether that means reviewing a draft together, joining a campaign build, or listening to a sales call. Ask specific questions about tradeoffs, constraints, and reasoning. Contribute ideas in the moment, then assign clear ownership and step back. Track whether your feedback references real details from current work. That practice keeps your judgment sharp, strengthens trust, and ensures your strategic decisions reflect the reality your team operates in every day.

Back to the top ⬆️

Why Critical Thinking Skills Drive Marketing Career Growth

Marketing knowledge expires at an alarming rate. Jenna felt that sting when she revisited old automation and lead scoring decks from a few years ago. Slides that once felt advanced now read like artifacts from a different era. Channels have shifted. Tool stacks have multiplied. Entire job descriptions have morphed in under five years. Anyone tying their value to a specific platform or tactic stands on unstable ground.

Jenna keeps her teams anchored in first principles. The mission remains steady even when the mechanics evolve. Marketing still revolves around moving a defined person toward a defined action, whether that action is a purchase, renewal, or upgrade. She frames it simply:

“It’s like baking. You have the same core ingredients. Sometimes you add a few new ones. The difference is the order and how you combine them.”

That analogy carries operational weight. The ingredients are channels, messaging, creative, timing, distribution. The order is sequencing, prioritization, and judgment. When leaders focus on judgment, they build operators who can reconfigure the recipe as conditions change.

When asked how leaders can actively develop thinking instead of just pushing for output, Jenna points to pattern spotting and deliberate stretch. She watches for people who adapt quickly and who show curiosity beyond their lane. She then nudges them into adjacent territory. On her team, that has meant encouraging someone hired as a copywriter to film content at an event, edit short-form videos, and test distribution channels. The title stayed constant, but the capability expanded.

Leaders can operationalize this immediately. Start with three concrete moves:

1. In your next one on one, ask each team member which part of the funnel they understand least and assign them ownership of a small project in that zone.
2. During team reviews, ask people to explain why they made a sequencing decision, not just what they produced.
3. Publicly recognize thoughtful tradeoffs, even when the experiment underperforms, because thoughtful tradeoffs build judgment.

Jenna believes it is faster to grow a strong operator than to hire a narrow specialist for every new initiative. Job descriptions serve as scaffolding, not ceilings. When leaders create psychological safety and signal belief in someone’s potential, high performers expand into ambiguity. Over time, the team develops shared pattern recognition. They recognize how demand behaves, how timing affects conversion, and how to reassemble the same ingredients in a smarter order.

Key takeaway: Build judgment by designing stretch into the job. Assign adjacent problems that require new tools or cross functional coordination. During reviews, evaluate reasoning and sequencing as rigorously as output. Track who consistently adapts and who stays curious under pressure. Over multiple quarters, those deliberate stretches compound into sharper decision making, broader capability, and durable career growth that outlasts any single tactic or platform.

Back to the top ⬆️

How to Build Business Judgment in Technical Marketing Roles

Business judgment grows in rooms where real decisions are being made. When asked how she balances business acumen with technical skill, Jenna goes straight to behavior. She tells her team to listen closely to what people are actually asking for, especially in cross functional settings like weekly sales calls. She wants them to pay attention to tone, urgency, and the questions hiding underneath the slide deck.

“Really listen to what people are asking of you. What are they trying to figure out?”

You might walk into a sales review thinking your job is to present a clean report. Jenna pushes for more. She wants you to study the room. Notice where people lean forward. Notice which numbers trigger tension. Ask yourself:

• What decision is this data supposed to inform?
• What pattern are they searching for?
• What risk are they trying to reduce before the quarter closes?

When you start anticipating those needs, you shift from reporter to advisor. Sales leaders begin to see you as someone who can help them predict what comes next. That is when technical skill turns into leverage.

Jenna also gives direct advice to highly technical marketers who feel stuck on the implementation side. You cannot rewire your brain overnight. You grow by attaching yourself to someone with strong business instincts and building together. Sit next to the revenue leader. Co create forecasts. Argue through tradeoffs. Model scenarios. Feel the pressure of a target that has to be hit, not just calculated.

That pairing does something powerful. It sharpens your technical work and expands your field of vision. Over time, you become the person who can see patterns, guide tradeoffs, and translate ambiguity into action. Jenna calls that becoming a linchpin. Leaders start coming to you early, before decisions are locked in.

She also has strong views on prioritization, and this is where many teams stumble. A backlog gets reordered and everyone adjusts quietly. High performers interrogate the why behind the order. They weigh impact across the organization instead of reacting to the loudest stakeholder. They think in terms of business goals, not ticket velocity.

Jenna draws a clean line between operators who grow and operators who plateau. Growth requires thinking bigger than your personal task list. Your work exists to move the organization forward. When you optimize for enterprise level impact, you build judgment. When you question assumptions respectfully and back it up with data, you earn trust. That trust compounds.

Key takeaway: Business judgment develops through deep listening, close partnership with commercial leaders, and a relentless focus on organizational impact. Technical skill gets you in the room; optimizing for business outcomes makes you indispensable.

Back to the top ⬆️

Why Confidence Without Humility is Dangerous

Overconfidence spreads quickly in AI conversations. Leaders publish bold predictions about autonomous buyers, fully agentic funnels, and platforms that will replace entire teams. Jenna distrusts certainty that sounds airtight. She believes leadership in this moment demands courage to move and humility to expect change.

When asked why humility feels so critical right now, she answered directly.

“You need the courage to act, but the humility to know that you’re probably wrong, or that this is going to change.”

That posture shapes how decisions get made. Every organization operates with incomplete information. Even the most obsessive reader can only process so much in a 24 hour window. You skim research, absorb newsletters, listen to operators, and still hold only a partial map of what is happening. Jenna accepts that constraint as a permanent condition. Leaders must decide anyway.

She wants teams to move with urgency. She also wants them to acknowledge risk in writing. Inside her teams, that discipline looks concrete:

• State the hypothesis behind the AI investment.
• Document the revenue assumption driving the bet.
• List operational and reputational risks before launch.
• Set a calendar date to revisit the decision with fresh data.

Fear plays a productive role here. A measured sense of risk keeps teams alert. It forces someone in the room to ask whether the model output is reliable, whether the integration is stable, and whether the customer impact has been considered. High confidence without this internal tension creates fragile systems and inflated promises. Founders often operate on conviction because they need velocity to survive. Operators inside scaling organizations manage a broader blast radius. Their decisions affect payroll, brand trust, and long term credibility.

Jenna treats humility as an operating discipline rather than a personality trait. She invites disagreement in planning sessions. She encourages leaders to surface what could go wrong before celebrating what could go right. That habit creates a culture where changing course feels responsible rather than embarrassing. In AI strategy, the environment shifts faster than most roadmaps. Leaders who admit uncertainty early preserve room to adapt without drama.

Key takeaway: Pair every AI initiative with a written hypothesis, a documented revenue assumption, a list of concrete risks, and a scheduled review date. Share these four elements with your team before execution and revisit them after 30 days. This practice builds disciplined speed, reduces preventable mistakes, and keeps confidence grounded in evidence rather than hype.

Back to the top ⬆️

How Revenue Leaders Prioritize Daily Energy

Energy becomes a finite budget when you run a revenue function and raise three kids under six. Jenna learned that capacity has edges. Earlier in her career, she responded to every email and cleared every inbox. She operated at full throttle because she could. Parenthood forced a recalculation. Time compressed, and expectations did not.

When asked how she decides what deserves her energy, she described a daily triage system grounded in consequence. She starts with one filter, what must happen today for work and home to function well. Everything else competes for space. Some emails sit. Some requests wait. She still mentors and volunteers, but she weighs each commitment against the reality of her calendar.

“What are the most important things that need to happen and what can slip?”

That question shapes her day. It pushes emotion out of the decision and replaces it with priority. You can apply the same lens. List what truly moves revenue, unblocks your team, or strengthens a relationship that matters. Then protect those items first.

Her energy map has three consistent pillars:

1. Core business impact, the work that drives measurable revenue or develops her team.
2. Family presence, school walks, dinners, and the ordinary moments that accumulate into memory.
3. Personal renewal, exercise, volunteer boards, hosting friends, conversations that expand her world beyond a screen.

Each pillar earns space on the calendar. Lower leverage tasks drift downward. Visibility for its own sake does not rise to the top. Constant responsiveness does not earn automatic approval. Leaders often confuse activity with contribution. Jenna organizes her days around contribution.

She also described contentment as a more stable target than constant happiness. Ambition still lives there. So does gratitude. She notices the texture of daily life, walking distance to school when the weather cooperates, the energy in a room she hosts, the shift in mood after a workout. Those moments inform her priorities. Energy flows toward what sustains her, because depleted leaders make reactive decisions.

Key takeaway: Install a Consequence Filter. Define three non negotiable categories that matter in this season of your life, for example revenue impact, family presence, and personal renewal. Every morning, identify one task in each category that must be completed that day. Execute those first. Defer tasks that do not clearly map to one of the three categories. Review your week every Friday and note where your energy actually went versus where it was intended to go. Adjust the next week accordingly.

Back to the top ⬆️

Episode Recap

Every company eventually operates inside a cobbled-together tech stack built under revenue pressure. Endless copies of spreadsheets to fill temporary gaps, manual processes for this one niche use case that stack up, and marketing and sales debt compounds quietly as everyone needs one new field. Marketing ops and RevOps leaders end up reconciling data across disconnected tools just to produce basic reporting. 

Jenna frames this ugly frankenstack tech debt as a leadership responsibility. It’s not usually the ops team that doesn’t want to fix the stack or the data. It’s usually because leadership is asking for quick wins. When executives refuse to pause and repair core systems, performance erodes over time. Strong leaders slow output when needed and reinvest in infrastructure so teams can operate with speed and clarity later.

Fixing that debt requires prioritization without perfect ROI math. Chasing exact calculations for every systems project stalls progress and its never actually accurate. Jenna shifts the lens to opportunity cost and revenue enablement. When operations teams spend their time generating ad hoc reports instead of identifying bottlenecks or shaping sales plays, the business sacrifices leverage. A clear signal appears when patchwork consumes more time than building. At that point, the stack constrains revenue velocity.

The conversation then turns to AI and decision making under uncertainty. Waiting for complete information creates inertia. Leaders build conviction through contained experiments that limit downside while generating real learning. Tool selection requires discipline. Teams should define a minimum improvement threshold before adopting new software and model the exit path in advance. They need clarity on where data resides, how it can be exported, and what retraining would cost if a switch becomes necessary within a year.

Jenna closes with career growth and the linchpin mindset. Technical knowledge depreciates, while judgment compounds through exposure and pattern recognition. High performers listen deeply in cross-functional settings and identify the business risks leaders are trying to manage. They stay close to execution so strategy reflects reality. They act decisively on directional data and remain adaptable as new signals surface. The through line is ownership, of systems, of decisions, and of personal growth.

Listen to the full episode ⬇️ or Back to the top ⬆️

Follow Jenna👇

• LinkedIn

✌️

—
Intro music by Wowa via Unminus
Cover art created with Midjourney (check out how)

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

Related tags

See all episodes

Future-proofing the humans behind the tech

Apple •Pocket Casts•Google •Overcast •Spotify •Breaker •Castro •RSS

• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed