DaedTech

Stories about Software

By

How to Delegate Effectively as Your Responsibility Grows

Editorial note: I originally published this on the Hit Subscribe blog.

I’m gearing up, like some kind of power washer, to spray new productized services into our operations group so they can SOP those services at scale.  And because I’m doing that, this seemed like a good moment to draw on my experience, both in leadership roles and as a management consultant, and lay out a blueprint for internal delegation.

I debated musing about this over on DaedTech, especially since programmers uniquely struggle when asked to delegate (for reasons I’ll get into in a bit).  But then I figured you marketers out there reading likely also have challenges when flipping from individual contributor (IC) to team leader in a growing organization.  So whether you’d have offered a penny or not, here are my thoughts on delegation.

Delegation as a Function of Org Chart

Let me start by explaining how successful delegators at each level of the org chart delegate to their direct reports, in broad strokes.

  • Executives: “You are accountable for this organizational goal.  Your deliverable to me is a plan and overseeing execution of that plan.”
  • Middle Management: “You are accountable for successfully executing this plan.  Your deliverable to me is judgement-based execution of the plan in a fluid environment.”
  • Supervisors: “You are accountable for these KPIs.  Your deliverable to me is executing the tasks that generate the KPIs.”

Now, let’s look at how ICs (and unsuccessful supervisors) tend to delegate.

  • ICs: “You are accountable for nothing.  Your deliverable to me is an execution of tasks to my exact specification.”

At the risk of restating the obvious, let’s pause here and observe something.  Successful delegation involves both tasks and accountability.  Unsuccessful delegation cedes only tasks and retains a vice grip on all accountability.

I don’t pay you to think!

Read More

By

Basking in the Traffic Gains: Our Content Refresh Early Detection System

I’ve made two posts this year about content refreshes.  One was about traffic recovery, and the other was about refresh identification. Both of them were, admittedly, fairly wonky.  I got lost in my SQL statements and graphs and invited you to come along for that ride with me, if you dared.

Not today, though.  Today is the day that I heed the demand, “In English, poindexter!”

I’m going to show off the easy button for refreshing content and realizing substantial traffic gains.  I can now do this because I’ve turned my queries and graphs into a dead simple, prioritized list of content to refresh.  You can explore it for yourself here (click “refresh candidates”), and this is what it looks like.

This is a screenshot from the alpha offering of our content performance monitoring dashboard, which I announced back in June.  (Beta coming soon!)  The dashboard here features our content lab and community site, Make Me a Programmer.

If you’re unclear on what a content refresh is or why you should do it, let me explain.  A content refresh involves making updates to an existing post or article on your site.  As for why you should do it, let me present an actual anonymized field study of the impact on traffic (refreshes executed on this group of URLs at the red dot).

If you’re sold on the concept, I’ll spend the rest of the post explaining how we help you do it, using our tooling and refresh-candidate identification methodology.

Read More

By

Organic Traffic Recovery: How to Win SERPs and Influence Execs

In the last few months, I’ve been burning the midnight oil.  By day, I run Hit Subscribe.  But by night and weekend, I’ve buried myself in a sea of client analytics data, building out our content performance monitoring alpha offering.

I say this not to complain.  After years of pretending to know what I’m doing in marketing, it’s fun to return to my roots of pretending to know what I’m doing in software engineering.  I mention the midnight oil because it has served as fuel for deep, interesting insights into refreshing content and traffic recovery.

And today I want to offer up those insights to you in the form of a clear, actionable traffic recovery playbook.

Setting the Scene: What Happened to Our Traffic?

Imagine that you’re responsible for content on your site and your organic traffic graph looks like this.

Sooner or later, you’re going to have an uncomfortable conversation about how and why you’ve presided over a 40% traffic decline.  From my outsider’s perspective, this most commonly occurs following an acquisition or perhaps a change in leadership.  After obligatory pleasantries, one of your first professional encounters is explaining this graph.

There’s a pretty good chance that you have many valid reasons.  Someone cut the content budget.  A staff writer quit and the backfill took forever.  The recent site redesign performs as well as a walrus on a unicycle.

But even as you say these things, they’ll sound like excuses to you.  And they’ll absolutely sound like excuses to the other party.

So here’s what you say instead:

I can do a detailed postmortem write-up on the traffic performance if you want.  But if you’re interested, I have an actionable plan for how to recover the traffic and I can show you that.

These two sentences will absolutely and completely reset the conversation.  You just need to be able to deliver on the actionable plan.  And that’s what I’m going to hand to you in the following sections, drawing on our now-unfair advantage of tons and tons of data.

Read More

By

The Best Tool for Real Content Attribution? The Fermi Problem

I was recently scrolling through LinkedIn, admiring the art of the single-line hook followed by emoji bullets, when I stumbled on a really interesting question from Fio Dossetto.  The question is as follows:

As someone who self-identifies as neither a marketer nor “smarter than” anyone, I figured I’d leave the comments to the thought leaders and call it a day.  But I couldn’t get the question out of my head, especially since some variant comes up so frequently in discussions with clients.

So in this post, I’ll offer the two cents nobody asked for on the subject of challenging content attribution.

Read More

By

The Flat Squirrel Barrier to Content at Scale

Editorial note: I originally wrote this post over on the Hit Subscribe blog.

Be decisive.  The road of life is paved with flat squirrels who couldn’t make a decision.

I don’t know who originally said this, so I can’t properly attribute it.  I guess that makes it some kind of piece of folk wisdom, now best suited for cheugy merchandise.

But whoever dreamed it up has a gift for impactful figurative language.  I’m sure you can picture the situation — your car barreling down on some hapless squirrel who starts left, then right, then backward, then splat.  Had the squirrel run in any direction, it would have met a better fate than it did by fretting to literal death about the decision while doing nothing.

I’m setting the stage with this gruesome metaphor to make my point here memorable.  And my point here is that collective flat squirrel syndrome is going to be your organization’s single biggest barrier to content and funnel metrics at scale.  (And I should note this only applies to customer acquisition strategies that require and substantially economize on scale: SEO, communities, parasocial followings, podcasts, etc.)

Here are some things you might think would be the problem but aren’t:

  • It’s so hard to find good writers.
  • The keywords in our space are super competitive.
  • {Insert our audience here} is such a picky audience.
  • There just aren’t any public distribution channels where our audience hangs out.
  • So few people know how to talk shop to our audience.

Nope, nope, nope, nope, and…drumroll, please…nope.

Those problems are all actually relatively easy to solve compared to flat squirrel syndrome.  The reason for that gets a bit into org theory but suffice it to say that this problem is intractable because it’s human nature and because the solution has to come from within, unlike all of the logistical issues above that can be solved with staffing and experimentation.

Read More