The Pipeline Progression Chart:  Why I Like It Better Than Just Tracking Rolling Four-Quarter Pipeline

When asked, “how is it going?” many companies will respond with something akin to, “things are looking strong, the pipeline is up to $50M.”

Not a bad statement, but certainly an imprecise one.  “Over what timeframe?” you might ask.  To which you’ll typically hear one of two answers

  • “Uh, that’s the whole thing.” I don’t love this answer as many companies –particularly the ones who answer with all-quarter pipeline — let junk opportunities get parked in the 5Q+ pipeline.  (You can fix this by including a timeframe as part of the definition of opportunity and ensuring you review the entire pipeline whenever you do a pipeline scrub.)
  • “That’s the rolling four-quarter (R4Q) pipeline.” I don’t love this answer either because, in my experience, companies who focus on R4Q pipeline as their top pipeline metric tend not to put enough emphasis on pipeline timing.  It’s too easy to say in January, “this year’s number is $20M and we’ve got $50M in the pipeline already (2.5x pipeline coverage) so we are golden.”  The problem, of course, is if 80% of that pipeline is backloaded into Q4, then while “the year may look great,” you’re going to need to survive three wasteland quarters to get there.  Even if that $40M Q4 pipeline were real, which it usually isn’t, most sales VPs won’t be around in October to close it.

I never look at rolling-four-quarter pipeline for the simple reason that I’ve never had a rolling-four-quarter sales target.  We have quarterly targets.  Instead of looking at R4Q  pipeline and hoping it’s well distributed (over time and across sellers), my philosophy is the opposite:

Let’s focus on ensuring we start every quarter with 3.0x pipeline coverage.  If we do that, the year takes care of itself, as does the year after that.

Once you accept this viewpoint, a few things happen:

  • Someone needs to start forecasting day-1 next-quarter pipeline coverage. What’s the point of focusing on next-quarter coverage if no one is tracking it and taking corrective actions as needed?  As mentioned, I think that person should be the CMO.
  • We need to start tracking the progression of the pipeline over time. This quarter’s starting pipeline is largely composed of last-quarter’s next-quarter pipeline and so on.  Since there are so many ebbs and flows in the pipeline the best way to track this is via periodic snapshots.

Towards that end, here’s a chart I find useful:

Let’s examine it.

  • Each row is a snapshot of the pipeline, broken down by quarter, taken on the first day of the quarter. (Some allow a week or two, for pipeline cleanup before snapshotting, which is fine.)
  • We’re tracking pipeline dollars, not opportunity count, which generally works better if you have a range of deal sizes and/or a multi-modal distribution of average sales prices. Doing so, however, can leave you overconfident if you create new opportunities with a high placeholder value.  (See this post for what to do about that.)
  • We show pipeline coverage in the block on the right. Most people want this-quarter coverage of around 3.0.  Targets for next-quarter and N+2 quarter are usually less well understood because many people don’t track them.  Coverage needed in the out quarters is a function of your sales cycle length, but the easiest thing is to just start tracking it so you get a sense for what out-quarter coverage normally is.  If you’re worried about that 1.6x next-quarter coverage shown on the 7/1 snapshot, read this post for ideas on how to generate pipeline in a hurry.
  • It’s good to carry at least one year’s prior snapshots so you can see historical progression.  Even more is better.
  • I’m assuming bigger deals and longer sales cycles (e.g., 6 to 12 months) so you will actually have material pipeline in the out-quarters.  For a velocity model with 25-day sales cycles, I’d take this template but just switch the whole things to months.

The most fun part of this chart is this you read it diagonally.  The $7.5M in starting this-quarter pipeline at the 7/1/21 snapshot is largely composed of the $6.5M in next-quarter pipeline at the 4/1/21 snapshot and the $3M in pipeline at the 1/1/21 snapshot.  You can kind of see the elephant go through the snake.

When you add this chart to your mix, you’re giving yourself an early warning system for pipeline shortages beyond simply forecasting starting next-quarter pipeline.  You should do this, particularly with big deals and long sales cycles, because one quarter’s notice is usually not enough time to fix the problem.  Yes, you can and should always try to mitigate problems (and never give-up saying, “looks like we’re going to hit the iceberg”), but if you give yourself more advance notice, you’ll give yourself more options and a better chance at reaching the goal:  starting every quarter with 3.0x coverage.

Add this slide to your QBR template now!

How Should CEOs Answer the Question, “What Keeps You Up at Night?”

I’ve always felt that “what keeps you up at night?” was a trick question for CEOs.

There’s one part of it I’m quite sure about.  There cannot be anything that you control that keeps you up at night.  Why?  Because you’re the CEO.  If something is keeping you up at night, well, do something about it.

Stress, as I like to say, is for VPs and CXOs.  They’re the ones that need to convince the boss about something.  They’re the ones worried about how something might look.  The CEO?  Well, you’re accountable for results.  You get to make or approve the decisions.

If you’re a founder/CEO then you shouldn’t be particularly worried about how things look to the board.  It’s your company.  You’ve got an invisibility cloak that your hired CEO counterparts lack, and which you should use when needed.  Think of founder privilege the way the kitschy Love Story described love:  it means never having to say you’re sorry.

For what it’s worth, and I won’t claim to have been God’s gift to CEOs, I lived by the control rule — that is, if I controlled it and it woke me up in the middle of the night, then I was going to do something about it.  That’s why one of the worst things I could say to one of my VPs was, “I woke up last night thinking about you.”  If that happened, and it sometimes did, then either our working relationship or their employment status was changing soon.

I put this in the same “listen to your gut” class as the I don’t want to talk to you anymore rule.  If you’re one of my VPs, then you’re running a key part of my company, then I should look forward to speaking with you each and every time.  If I don’t look forward to speaking with you, it’s a massive problem, and one I shouldn’t ignore.  After all, why wouldn’t I look forward to speaking with you?  Who don’t I like speaking to?  People who:

  • Don’t listen
  • Don’t follow through
  • Can’t keep up
  • Grinf-ck me
  • Can’t or won’t change
  • Are negative
  • Are mean

There are probably other classes, but the point is if I don’t want to talk to someone, it’s a huge signal and one I should dig into, not ignore.

Waking up in the middle of the night is an even bigger signal.  If you agree that CEOs should not wake up in the middle of the night over things they can control, then we can move onto the second category:  things they can’t control.  Should CEOs wake up in the middle of the night over them?

Again I say no.  Why?

Making bets is a big part of a CEO’s job.  Based on available information and working with the team, the CEO places a set of strategic bets on behalf of the company.  The company then needs to execute those strategies.  While the quality of that execution is under the CEO’s control (and should be high to remove execution as a source of noise in the strategy process), the outcome is not.

Why be stressed while the roulette wheel is spinning?  It’s a natural reaction, but does it change the outcome?  You’ve placed your chips already.  Does stressing out increase the odds of the ball landing on your square?  Does not stressing out decrease it?  No.  It changes nothing at the roulette table.

I’d argue that in business, unlike roulette, stressing out can effect the outcome.  A CEO who’s constantly under stress while the wheel is spinning — e.g., waking up in the middle of the night — is likely to perform worse, not better, as a result.

  • A tired CEO does not make great decisions
  • A haggard CEO does not inspire confidence
  • A grumpy CEO does not handle delicate situations well

I’m not trying to minimize the very real stress that comes with the CEO job.  I am, however, trying to provide a rational, contrarian, and hopefully fresh point of view that helps you better frame it.

In the end, there are two types of things that CEOs can potentially stress about:

  • Things they can control.  They shouldn’t stress over these because they should do something about them, instead.
  • Things they can’t control.  They shouldn’t stress over these because doing so will not change the outcome.  Worse yet, it may well change the outcome — for the worse — over the things they can control.

Ergo, CEOs should never stress about things.  QED.

As Warren Buffet said, “games are won by players who focus on the playing field — not by those whose eyes are glued to the scoreboard.”  Focus on what you can control and, as Bill Walsh says, the score will take care of itself.

Congratulations.  You’re the CEO.  You’ve got the best job in the world.  Enjoy every day.  And sleep well every night.

# # #

Notes

  • To reiterate, none of this is to trivialize the stress that comes with the CEO job nor to suggest that CEOs shouldn’t work hard.  It is to say that I believe they will be happier and more effective if they find a way to sleep well — as most senior executives do.
  • To look at this from an outcomes perspective, while I was pleased with the operational results at both companies I ran, I was not particularly pleased with the outcomes.  Did I work hard and obsess about things?  Yes, in general.  If I worried more and slept less do I think it would have improved my outcomes?  No.  Were some of the worst decisions I made in part due to being worried and stressed about things?  Yes.  Did I in general sleep well?  Yes.  I have always naturally focused on running plays well and believed that the score would then take of itself.  In my experience, sometimes it does, but sometimes it doesn’t.
  • In writing this post, I found a few anecdotal, fun, and one somewhat ironic article on success and sleep.
  • This Bill Walsh quote seems to undermine my argument.  “If you’re up at 3 A.M. every night talking into a tape recorder and writing notes on scraps of paper, have a knot in your stomach and a rash on your skin, are losing sleep and losing touch with your wife and kids, have no appetite or sense of humor, and feel that everything might turn out wrong, then you’re probably doing the job.”  That said, he’d use this as an opener to speeches which were largely about focusing on what you can control.
  • Walsh’s other quote on sleep was more proactive:  “If you want to sleep at night before the game, have your first 25 plays established in your own mind the night before that. You can walk into the stadium and you can start the game without that stress factor. You will start the game and you will remind yourself that you are looking at certain things because a pattern has been set up.”

Marketing’s Uncomfortable Relationship with the Truth

Advertising is legitimized lying,” said the English writer HG Wells.  Pop marketing guru Seth Godin wrote a book entitled, All Marketers Are Liars (but cleverly redacted the title).  Google suggestions reveal that people have plenty of questions about the authenticity of marketing:

People Also Ask

Another marketing book adapts the famous Mark Twain quote about statistics:  Lies, Damned Lies, and Marketing.

Let’s just say that in the minds of many people marketing seems to have an uncomfortable relationship with the truth.  In this post we’ll explore that relationship via a number of stories I have seen and experienced over the course of my career.

Telling the Truth in the Most Positive Possible Manner
One of the first press releases I reviewed when I took over product marketing at Business Objects (long, long ago) bore this title:

Business Objects Ranked #97 on the Software 100

Was that true?  Yes, we were number 97 on this; we just squeaked in there.  Phew.  But were there alternative also-true ways to say the same thing?  Indeed, yes:

Business Objects Named to the Software 100 Ranking

Both statements are true.  Marketing should be about telling the truth in the most positive possible manner.  But does it have to be the truth?  Yes.  That was a constraint in my mind for three reasons:

  • Moral.  I don’t want to lie.  I don’t want my craft to be about lying.
  • Effectiveness.  I want my marketing to be effective.  That means it must be credible.  If you believe that customers always figure it out in the end, then lying is not only immoral, but ineffective.
  • Legal.  There are numerous laws in play here and companies get sued for breaking them.  While I’m no lawyer, I do believe that a good marketer should not expose their company to needless legal risk, especially when doing what’s both otherwise immoral and ineffective marketing — a potential triple crown of shame.

Unlike this TechTarget article, I don’t think “spin” is intentionally misleading.  It is, however, intentionally positive both in expression and point of view.

Truth in Advertising
Say you walked into a store and someone promised you this:

Whopper as Advertised

So you ordered one, and then they gave you this:

Whopper as Delivered

You’d likely be a bit disappointed, as was Walter Coleman who bought a Whopper (excuse the double entendre) in the state of New York and who, according to the class-action complaint, “expected the burgers that he purchased to be similar in size to the pictures of the burgers in Burger King’s advertisements and on Burger King’s store menu ordering board.”

The lawsuit alleges that Burger King violated the New York Deceptive Acts and Practices Act, N.Y. Gen. Bus. Law § 349 and similar laws in the other 49 states.

This is a class action against Burger King for unfair and deceptive trade practices concerning the sale of certain falsely advertised menu items.  Burger King advertises its burgers as large burgers compared to competitors and containing oversized meat patties and ingredients that overflow over the bun to make it appear that the burgers are approximately 35% larger in size, and contain more than double the meat, than the actual burger.

The legal system will decide how Burger King fares against these claims. At a high level, I believe you can make one of two arguments:

  • The marketing is deceptive, portraying a burger that is larger, fresher, and presumably tastier than the one delivered.
  • Or, unless you are from Mars, everyone knows that food photography is exaggerated by food stylists and that generally no food product ever looks as good as it does in the advertisement.

The second point argues that the pictures are effectively visual puffery, i.e., marketing claims that are harmless exaggerations that no reasonable person would believe (e.g., our detergent makes towels whiter than white).

Puffery is a valid defense against a false advertising claim.  And I can’t help but link to this cleverly-titled article when discussing puffery:  The Best Explanation and Update on Puffery You Will Ever Read.

The Lanham Act
While there have been some changes since my first encounters with it, the law that immediately springs to my mind is the Lanham Act, because that was the law usually referenced when I was on the receiving end of complaints.

Enacted in 1946, the Lanham Act addresses both trademarks (which we’ll largely skip today) and competitive practices, the latter including false advertising, which includes:

  • Advertising as well as other forms of promotion such as brochures, flyers, and presentations — and even, if widely disseminated, oral statements.  (So be careful what you train your sellers to say.)
  • False or misleading claims about your products (e.g., our snake oil cures baldness).
  • False or misleading comparative claims whether explicit (e.g., we have feature X and competitor Y doesn’t) or implicit (e.g., only we have feature X).

Quoting this article:

To prevail on a false-advertising claim under the Lanham Act, a plaintiff must satisfy the following elements: (1) a false or misleading statement of fact; that is (2) used in a commercial advertisement or promotion; that (3) deceives or is likely to deceive in a material way; (4) in interstate commerce; and (5) has caused or is likely to cause competitive or commercial injury to the plaintiff.

Thus, defending a claim made under the Lanham act usually takes the form of:

  • Truth.  The claim is true, regardless of whether it’s negative about or injury-causing to the other party.
  • Puffery, which is not likely to cause deceit because, by definition, no reasonable person would believe the claim (e.g., “the world’s best cup of coffee,” Buddy the Elf notwithstanding).
  • Opinion.  Testimonials are unlikely to cause deceit as the audience should realize that when the endorser says, “it’s the best coffee I’ve ever tasted,” that this is a statement of opinion, not fact.
  • Precision.  I didn’t see this in the legal articles I found, but I know there is a difference between saying, “our widget reduces energy consumption by 80%” and “our widget reduces energy consumption by up to 80%.”  I believe such precision (aka, weasel wording) can help you defend a claim provided the claim, in its context, isn’t otherwise proved misleading, even if precisely true.

For more information, see False Advertising Litigation 101: Some Like it Misleading or Checklist for Suing (or Being Sued) under the Lanham Act.  Read both if you’re a marketing leader unfamiliar with this territory.  Try to read about a few recent cases as well (e.g., Pom Wonderful vs. Coca-Cola, Millercoors vs. Anheuser-Busch, or Chobani vs. Dannon).  Most of the cases are consumer products, but the law remains the same in technology.

Product Marketing Claims
The beauty of solutions-oriented marketing is that you generally get to steer free of legal problems.  As long as you describe a problem faced by a buyer (e.g., forecast accuracy) and how your product helps the buyer solve that problem (e.g., AI/ML-based forecasting), you should generally be safe.  As long as your product actually does help solve that problem.

Product marketing gets a bit more tricky for a few reasons:

  • The veracity of feature/benefit claims.  Does your distributed architecture really deliver improved scalability?  Or do other implementation bottlenecks limit scaling well before architecture becomes the limiting factor?
  • The veracity of speeds-and-feeds claims.  Precision, ranges, and limits are your friends here.  Reduce energy consumption by up to 80%.  Cut typical processing time, by 20 to 40%.
  • The desire for differentiating claims.  Sales wants silver bullet features: only we have feature X or Y.  Reality is seldom that black and white.  Don’t fall victim to pressure to position something as unique when it isn’t.
  • The temptation to brand features and tread into the other half of the Lanham Act, trademarks.  Don’t do it.  Set the agenda instead.

Aside:  Setting the Agenda
Tech marketers sometimes get confused and think that a customer evaluation framework (e.g., a multi-column spreadsheet with features in the rows, a weight column to weight the importance of each feature, and a score column per vendor to rate each offering) is fixed — and thus their job is to maximize their product’s scores relative to the competition.

That view is myopic.  The most powerful technical marketing influences the framework itself by selling which features should qualify as rows.  Sometimes called “defining the playing field” — or if you’re changing an already-established evaluation framework, “moving the goal post” — these are both forms of what I call, “setting the agenda.”  That is, convincing people that your most powerful, differentiated features are the ones that matter most, and if you’re successful, then the matrix takes care of the rest.

To pick a real, but ancient, example.  Back before databases could execute procedural code, they could only evaluate SQL statements to select, update, insert, or delete rows in tables.  More than 30 years ago, Sybase changed all that by introducing stored procedures that included SQL statements, variables, and conditional logic.  The benefits of stored procedures were speed thanks to compilation (as opposed to repeatedly re-interpreting the same statements) and reduced network traffic (due to less client/server communication).

But instead of either patenting the invention or trademarking the name, they decided to set the agenda.  Give the feature a common name (i.e., not a trademarked name like Intelliprocs), make sure the market knew they invented the feature (through PR/AR and product marketing), and explain to buyers why they should shop for that feature (i.e., why that feature deserved a row in their evaluation spreadsheets).  When you do product marketing in this way, you’re not making Harvey Balls that competitors will sue you over and that customers won’t believe anyway.  Instead, you’re fighting to get your truly differentiated features rows in the spreadsheet and then, well, the rest takes care of itself.

Over time, of course, competitors counter these features and you need to make new ones.  But over time analysts will remember who’s innovating in the market, and in which direction (so ensure you have a bigger strategic narrative) and they’ll know who’s copying.  For more on how to stay ahead of this process, see my post entitled, The Market Leader Play.

Back to our subject, this approach keeps you out of messy and sometimes litigation-prone business of making specific comparative claims about features and benefits.  But sometimes, you have to do just that.

Comparative Claims
My first job in marketing was competitive analyst.  There is a time and a place for specific competitive claims and we’ll cover that now.

There are two types of situations in competitive:

  • Choir preaching.  You’ve already won the deal in the mind of the buyer and they are looking for reassurance and/or to help sell the decision, typically against light resistance, internally.  If you oversell here you can risk losing the deal so you want simple, high-level messages and tools that confirm the buyer is making the right, safe, and logical choice.
  • Mind changing.  You’ve lost the deal and you need to fight your way back in.  You need hard-hitting messages and tools to say, “you’re about to make a serious mistake and I’m trying to help you prevent that.”  While this is inherently a Hail Mary pass, you need to be careful you don’t do anything so crazy that you preclude your fallback plan of, “Only sign a one-year deal with BadCo and then you can re-evaluate and pick us.  Let’s stay friends.  You’ll see.”

There are three types of messages in competitive:

  • Positioning.  High-level messages that physically or metaphorically lay out a map of the market and position vendors on it.  For example, they’re a last-generation solution with an old architecture.  Or, they’re a point-solution for 1/3rd of stated problem.  Or, they’re an SMB solution trying to come up-market (and you have an enterprise-class problem).  Positioning is imprecise and non-scientific, but powerful.  It is great for choir-preaching and can be effective for mind-changing if it’s good.  Legally, it tends to be safe because the claims are high-level and imprecise.  My favorite technique here is what I call a 3+1 repositioning.
  • Product differentiation.  Detailed messages that map customer problems to features and compare the effectiveness of your vs. your competitor’s features to solve the problem. These are hard to do and they have to be 100% correct from both a marketing and legal viewpoint.  Remember, in enterprise sales there are typically champions for each finalist vendor and they will fight this out.  It works best when the “feature” is high-level (e.g., an AI engine, an entire product) and the differentiation is black/white vs. gray.  Otherwise, it’s quicksand.
  • Character assassination (i.e., vendor viability attacks).  These are common in enterprise software —  particularly when there is size/funding disparity among the vendors —  and while these fear-based attacks can leave a bad taste in the buyer’s mouth, they nevertheless often work.  Also known as selling FUD, these attacks take the form of, “I hear they’re running out of cash.”  There is nothing more pathetic than watching a seller who’s spent their entire career at large, market-leading companies go deer in the headlights  when first hit with one of these attacks at a startup (think:  “We are?  I knew it!”)  A skilled CFO is the best person to answer these questions and smart sellers nonchalantly offer to setup a call with the CFO to address any concerns.  To my chagrin, I’ve never found a lawyer who finds such tactics actionable, so I’ve come to accept them as a sales problem, not a legal problem — even if in the back of my head, I sometimes still wonder.

Does All This Matter?  A Closing Story
The net of all this is pretty simple.  Understand the law as part of your professional responsibility as a marketer.  Then:

  • Talk about solutions first
  • Positioning second
  • Features/benefits third
  • Differentiation last
  • And when you make claims, be precise and careful that they’re true

In a world where it’s pretty clear that many marketers don’t do this, once in a while you start to wonder if it’s all worth it.  Why not be sloppy and fail to make precise leadership, uniqueness, and differentiation claims?  Even the faithful sometimes do wonder.

Then one day, you do an investor meeting at a public company.  The investor works at a large fund that has a $60M position in your employer.  They show up with your last three press releases, highlighted.  They walk through each release, in order, challenging you on every highlighted phrase.  You have conversations that sound like this:

Investor:  It says here that you’re the leading query, reporting, and analysis tool.  That’s not true.  Cognos is bigger.

You:  No, it doesn’t.  It says we’re the leading integrated query, reporting, and analysis tool.  Cognos isn’t integrated.  PowerPlay and Impromptu are separate products.

And then, for me at least.  It was all worth it.  Maybe a lot of people fail to notice when you’re rigorous and truthful in your marketing claims.  But some important ones do.

# # #

Disclaimer:  I am not now nor have I ever been a lawyer.  This post is not legal advice.  See FAQ for additional terms, conditions, and disclaimers.

 

Crash Course in Customer Success SaaS Metrics: Appearance on the ChurnZero podcast.

Earlier this week I appeared on a webinar with You Mon Tsang, founder and CEO of ChurnZero, a SaaS application aimed at helping subscription businesses reduce churn.

In this post, I will share the video of event, provide a link to the slides, provide a link to the Q&A wrap-up they posted, embed the video below, embed the slides below that, and finally provide a quick summary below that.

Here’s the video:

Here’s a copy of the slides:

Here’s a quick list of the topics we discussed:

  • ARR and MRR, and when to use which
  • Logo retention rate, why a count-based rate works best when your customers are more or less “all the same” on deal size, and that you should use a dollar-based rate when they’re not.
  • Available-to-renew (ATR) logo retention rate, which factors in only those customers who had a chance to renew or not.  If you’re an ARR-based company but do multi-year contracts not every customer has the chance to get out every year.
  • Gross revenue retention rate, and why it’s gathering steam as an important metric.  (Sometimes great expansion is hiding major churn and just looking at churn before expansion will reveal that.)
  • Net revenue retention (NRR), aka net dollar retention (NDR) for those who work only in dollars, which is probably the hottest SaaS metrics after ARR and ARR growth.
  • Lifetime value (LTV), and its fairly severe limitations.  I gave a talk on this at SaaStr two years back.
  • Customer acquisition cost (CAC) and the CAC ratio.  How it differs for new customer and expansion ARR.
  • LTV/CAC ratio.  An attempt to measure what something costs against what it’s worth, but one that has generally failed and is now being replaced by NRR.
  •  Benchmarks for many of these metrics from the KeyBanc 2021 SaaS Survey.

Thanks to all those who attended and thanks to You Mon for inviting me and Cori for executing it so well.

Understanding SaaS Marketing as an Investor — Appearance on The Novice Investor podcast

Just a quick post to highlight a video / podcast episode I recently recorded with Cillian Hilliard, fellow board member at work management leader Scoro, and investor at Kennett Partners.  Cillian runs a great blog (complete with detailed financial models) at The Novice Investor.

(Understanding SaaS Marketing as an Investor – Dave Kellogg from Cillian Hilliard on Vimeo.)

In the episode we discuss:

  • Pipeline, which is used by investors to evaluate trajectory, and how to evaluate a pipeline and tell if it’s real, which ultimately comes down to what I call pipeline discipline.
  • Common problems in the pipeline including air, rolling hairballs, sudden changes / gaming, squatting, tantalizing pipeline, and excess coverage.
  • Detecting repeatability in the sales model and the validity of “just add water” kind of claims.  How to detect gaming.
  • The floating bar problem.  The thinner the pipeline, the lower sellers sets the bar on acceptance and conversely.    The chick/egg problem with pipeline that results.
  • The risks of math and MBA types becoming over-reliant on numbers / models, and how to manage them.  Remember the George Box quote:  “all models are wrong, some are useful,” which I discussed in my SaaStr 2021 presentation.
  • Mitigating this problem by “just talking” and doing periodic win-touch analysis to keep you connected to reality.
  • The attribution problem and my new favorite mug.  How to present attribution data to avoid problems and over-reactions (hint:  put disclaimers up front).

Thanks Cillian for having me on the show.