Home / Blogs

Challenges for .brands - How to Engage Internal Stakeholders

This is the third in a series of blog posts discussing the strategic and operational challenges faced by .brand TLD owners and the processes involved in getting them ready for use. Previously we discussed the delegation process, which you can read here.

Developing a .brand TLD strategy requires resources and input from almost every function in your organisation.

Unfortunately, most organisations that applied for a .brand TLD have successfully de-prioritised the project to the point where even the executives who signed off on the project in 2011/2012 may need to be reminded what it is.

Funding allocation may or may not still exist. Your digital brand roadmap may or may not include reference to the TLD. You’re essentially starting an internal awareness campaign from scratch.

Yet the stakes couldn’t be higher. Think about the importance of your .brand TLD. To achieve its potential, it will eventually become the backbone for your digital brand. And in today’s business landscape, you can replace ‘digital brand’ with simply ‘brand’.

To add to this challenge, the project won’t succeed without support from across your organisation. Just try to think of an area that will NOT be impacted in some way by your .brand TLD.

To develop a strategy for your .brand TLD, you’ll need to spend considerable time with senior stakeholders in a workshop environment in order to explore options and agree on a strategic direction.

There is one guiding principle that rises above all others when organising your strategy workshop; the need to engage every facet of the organisation. You will need to bring together senior people from all functions—preferably at the executive level.

Why? Three reasons:

  1. There is never a shortage of good ideas, but the real challenge is in prioritising them. Opportunity must be balanced against risk, which requires all impacted functions to be represented.
  2. Even if senior stakeholders don’t love the final strategy agreed in the workshop, at least they were involved in its creation. This means they will (almost!) never shoot it down later, and are much more likely to actively support it with time and resources.
  3. You can’t do this on your own. In order to share the workload of launching and operating the .brand TLD, you need to start distributing the responsibility.

How to bring senior stakeholders together

We’ve held a number of workshops with major brand clients on developing their .brand TLD strategies. Achieving the right mix of participants in the room is always a challenge.

To understand why they should attend, people first need to understand what the .brand TLD is and how it impacts both their department and the whole organisation.

You’ll need a presentation that can capture that story. Remember that you’ll have an audience with differing priorities—what appeals to the marketing team will be different to what appeals to the IT folks. Communicate verbally wherever you can - with so many new concepts the message can easily become lost or confused.

Wherever possible, have the executive of your function raise awareness and gain buy-in from other executives. This will save you time and effort and greatly improve your chances of success.

Who needs to attend?

You need to involve senior stakeholders from all functions of the organisation. This will ensure risks are addressed and there is much less chance of internal roadblocks as you progress.

This doesn’t mean that you need the same level of representation from each function. As a general rule, the three areas which will need to be heavily involved in the strategy workshop are:

  1. Marketing (digital, agency, brand)
  2. Legal (risk, contracts, governance)
  3. IT (web, infrastructure, security)

Plan your approach

We know that change can create fear and uncertainty, and the prospect of launching a .brand TLD will likely be incredibly intimidating for some stakeholders. It’s understandable that some executives might intuitively seek to block the launch of a .brand TLD if it’s something that is being forced upon them, especially if they already have a heavy workload.

That’s why it’s important to engage these internal stakeholders early and seek their input and co-ownership of the .brand TLD project. If your internal stakeholders feel as though they’re included in the change and can influence the outcome, they will be more likely to support the cause.

Your strategy workshop for your .brand TLD is a critically important event. It is worth putting the effort in to bring together the most senior, influential stakeholders you possibly can.

By Corey Grant

Corey is part of the Registry Services team at Neustar, based in Australia. Neustar is the largest registry services provider by number of TLDs and are leaders within the ICANN community in policy and governance.

Visit Page

Filed Under

Comments

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

VINTON CERF
Co-designer of the TCP/IP Protocols & the Architecture of the Internet

Related

Topics

Brand Protection

Sponsored byCSC

IPv4 Markets

Sponsored byIPv4.Global

New TLDs

Sponsored byRadix

Cybersecurity

Sponsored byVerisign

Domain Names

Sponsored byVerisign

Threat Intelligence

Sponsored byWhoisXML API

DNS

Sponsored byDNIB.com