Leadership, Technical, and Human

Technology isn’t just about the technical. Not by a long shot. It starts and ends with people.

Of course technical expertise is required, no doubt. But why do so many technology projects end in disappointment or debacle even when the technical side of the equation is well covered?

The answer is that the technical is only one side of the equation, and — especially internally to an organization — not even the most critical side….

Read more

We strive to earn your trust with your inbox. We don't like clutter and we know you don't either!

The Curriculum

The Platforms Chief: "Protector of the Realm" and "Greatmaker"

The product team needs a chief. A great chief. A steward and protector, a guide and a field general. Every role on the team is important, but getting the right person steering the ship will differentiate whether the product team becomes an organizational gamechanger or just spends its time fixing things.

Read more

We strive to earn your trust with your inbox. We don't like clutter and we know you don't either!

The Curriculum

Put the Chief on Your Leadership Team

A fully-realized chief of the technology accelerator team (a.k.a. product team) is an executive team level position. Not having that voice on your leadership team is part of why your organization has been so consistently stumbling when it comes to its technology.

Read more

We strive to earn your trust with your inbox. We don't like clutter and we know you don't either!

The Curriculum

Flood the Zone with User Support

Is there any better investment than making sure what you’ve built is being used to its fullest potential?

Read more

We strive to earn your trust with your inbox. We don't like clutter and we know you don't either!

The Curriculum

The Improver Personality

It used to be that some lucky companies would just happen to hire someone who happened to have the gumption to say, “This could be better, folks.” But can you imagine a better investment than someone who is wired to constantly improve the way everything in your organization works?

Read more

We strive to earn your trust with your inbox. We don't like clutter and we know you don't either!

The Curriculum

You're Hiring for the Wrong Thing

A common mistake organizations make is hiring developers. This is technology, right? That must mean we need developers. Well not really, no….

Read more

We strive to earn your trust with your inbox. We don't like clutter and we know you don't either!

The Curriculum

Finding Great External Partners and Making Technology Magic

To reach a new level of orbit with your organization’s technology, you need a crack internal Technology Accelerator Team (a.k.a. Digital Product Team), but you ALSO need terrific external partners. Here’s how to find them.

Read more

We strive to earn your trust with your inbox. We don't like clutter and we know you don't either!

The Curriculum

What You're Getting for an Hourly Rate

We consistently advocate for outsourcing software development. Sometimes we’ll get pushback based on the cost of retaining external developers, especially when there are enough relatively extensive development needs that the organization is receiving costly developer invoices on a regular basis. But there are several reasons the outsourcing arrangement makes more sense than hiring internally…

Read more

We strive to earn your trust with your inbox. We don't like clutter and we know you don't either!

The Curriculum

Nobody Cares About Your Website Launch

Don’t send out an announcement about your new website. Nobody cares about your website launch. Unless…

Read more

We strive to earn your trust with your inbox. We don't like clutter and we know you don't either!

The Curriculum

Detangling Digital

If you ask five or ten different digital directors what their scope/remit is, the answers will be all over the map. You see completely different meanings of a Digital department from organization to organization. In some cases it refers to digital campaigning and organizing. In others it means writing and sending email. Some digital departments are made up of social media specialists. Still others feature traditional IT functions, and/or ownership of digital platforms like the CRM or website CMS.

If there is a clear singular function to the Digital department, then we’ve got no quarrel with it. If your Digital department is clearly focused on digital campaigning, for instance, you can call it whatever you like. 

The problems creep in when a Digital department becomes an excuse to mash together multiple disparate functions into a single home that strains to support them. In the most extreme cases, the Digital department may even be asked to include all of the above functions at once, with the reasoning that they all involve digital technology in some way. 

We liken that to the idea of having a “Department of Paper”, and insisting that all work involving paper must go through that single department. That concept is obviously absurd, but not too much more absurd than saying that all things digital nowadays go through a single digital team. How could that possibly work? How could anyone coherently manage communications, fundraising, social media, traditional IT, and tech platform development all together? How could you effectively prioritize, or manage such a complex combination of workflows? 

For some this may sound sacrilegious, since over the last decade or so the creation of a separate “digital” department often represented a hard-fought victory, wresting the control and management of all things digital away from staff who were masters of legacy systems and media but who were unfamiliar with how to harness the power of newer digital tools effectively.

But in today’s rapidly evolving world, we should admit that the big-D “Digital” umbrella has outlived its usefulness. 

Smushing together digital has real, problematic consequences. It distracts people from their core work, undermines priorities, misaligns incentives, and causes core functions to slip through the cracks. You’re left with a team that is usually overwhelmed, constantly being asked to do things outside their areas of expertise, and frustratedly rowing in different directions -- from each other and from others in the organization.
 

Tangled up in "Digital"

These days damn near everything is digital in some way, so we need more useful distinctions. When it comes time to untangle the undifferentiated digital mess, here’s a simple guiding principle: everyone should get to focus on their areas of expertise. Campaigners should spend their time campaigning. Communicators should spend their time communicating. Fundraisers should spend their time fundraising. IT staff should spend their time doing IT. Digital product managers should be evolving their digital products (such as CRM and CMS platforms). 

Each of these areas is a complex area of expertise that requires focus and care, and should be supported in a department that supports and enhances its mission. And each should be able use the tools of their trade, which these days, include digital tools and mediums.

If you’re a campaigner who needs to send an email, you should be able to work through and negotiate your content and sending schedule with your campaigning and communications colleagues. Then between those teams, someone should be able to pull up a template on the email system, populate your content, and schedule the message. And this should be able to happen without having to compete for priority and attention with people who are developing your CRM system, or A/B testing website donation page copy, or fixing your office printers. The workflows and skillsets for each are entirely distinct.

So at this point, we most commonly find ourselves recommending the integration of digital skillsets back into every department according to the area of expertise.
 

Sample digital functions within areas of expertise

 

For some organizations, this might only require a slight tweak -- a few meaningful adjustments to job descriptions. For others, it could take a radical re-organization, and those should never be undertaken lightly. But the appropriate structure for today’s organization should reflect the reality that a basic level of digital fluency can no longer ever be “someone else’s” responsibility, it must be everyone’s. 

And of course we’re not talking about every staff-member learning highly technical configuration and development skills! Those should remain specialized. We’re just saying every department needs to include people who know how to use the digital tools that are part of their trade. 

~

So once you get each of these other functions back to their home planets, is there still a need for any kind of digital specialization? Yes! Very much so! In fact, sorting those functions back out leaves a clearer focus on the key gap that remains, which is the critical work of managing your core digital platforms (such as your CRM and CMS). Give these responsibilities to people who are focused, talented, and aspiring to become masters of that work. That’s the heart of a digital product team.

So if you’re in charge of a Digital team and are finding yourself in the business of herding cats and balancing unreasonable expectations, take a moment to think about what is at the core of your remit, and perhaps more importantly the core of your interest and talent. What do you think success looks like? Whatever it is, could that become the clear focus of your team? And could the other functions of digital be moved to the spot in the organization where they can really thrive?

Everyone likes to geek out on something. Wouldn’t it be great, both in terms of staff happiness and organizational effectiveness, if people spent their time focused on the areas where they bring the most energy and talent to the table?
 


We strive to earn your trust with your inbox. We don't like clutter and we know you don't either!

The Curriculum