Archives for category: Marketing

In the seventh B2B product launch process step, we reviewed the outcomes of our efforts and hopefully learned some lessons to help us improve the next time.

So what’s the eighth B2B product launch process step? It’s the same as the last step of the B2B marketing process, the B2B buying process, and the B2B sales process. It’s back to the beginning, to the first step.

The cycle of the B2B product launch process is complete. As at the very beginning, we need to check our facts. We’re onto a new project, a new product launch, step one of a new launch process. Off we go – again!

Well, we executed the plan. We completed the sixth step of the B2B product launch process.

Now it’s time to see how we did. The seventh B2B product launch process step is to manage the outcomes of the project.

It’s important to manage the outcomes and compare them with the requirements and targets we set earlier in the process. One of the common mistakes is to move onto the next shiny toy and not review performance, so that you learn from your mistakes, celebrate the high points and be better the next time.

In managing those outcomes, it’s important to be fluid. In some areas you’ll have satisfied your requirements, and in some areas you won’t. If you nailed every target, then you probably weren’t ambitious enough.

A fluid approach helps you understand the poorer areas of performance. Did you fail to accurately capture your customer’s needs, or did you interpret their feedback wrongly? Which areas of the business did not deliver to target? What are the lessons learned?

A ‘lessons learned’ meeting, which should be a collaborative rather than a finger-pointing or scapegoat-finding exercise, is a great way to close out the project and feed the lessons – requirements, scheduling, resourcing, delivery – into the next project and across the business.

In our fifth B2B product launch process step, we made sure our people were ready to go.

In our sixth B2B product launch process step, we go. It’s time to execute the plan.

Of course, no plan ever goes absolutely 100% to plan, if you pardon the repetition. That’s why it’s always good to have a plan B, and perhaps a plan C. For the main pillars of your plan, what will do you if one of those pillars doesn’t stand up as you expect? For example, if you’ve decided for a ‘big bang’ launch, a good fall-back position is to go for a phased or soft launch, starting with a smaller, more manageable set of advocate customers, and moving from there.

During the execution phase, which might take place over weeks or even months, regular progress meetings with all the key players keep the project on track and allow you to take corrective action if key pillars fall behind, affecting the overall RAG – Red, Amber or Green – status of the project.

You’ve done much of the hard work, well done. In many ways, this sixth step is the easiest. It’s like when it comes to game-time. Everyone knows what’s expected of them, and what the steps are to deliver.

And now, for the next step, it’s time to see how you got on.

The trouble with social media is the trouble with the 2-way nature the Internet has developed into.

On the plus, it gives everyone a mouthpiece. It’s an amazing, equalising, liberating and democratising mechanism. We can all self-publish and let our thoughts be heard around the world.

On the minus side, it gives everyone a mouthpiece. Trolls, inadequates and other losers can spew forth their bile and vitriol from the relative safety of their device.

You see, traditionally, the rich, powerful and famous published, broadcasted and pontificated and we – the great unwashed on the receiving end of this 1-way traffic – absorbed and consumed it. They were the creme de la creme and there was in the main a relatively high standard and a degree of self-censorship involved. They understood the medium, and they controlled it.

Once you make the broadcast mechanism 2-way and universal, a lot of those conditions and controls go away. Suddenly the 99% of us get a chance, and we’ve far less to lose, and potentially a lot more to gain.

It’s not necessarily progress, or regress. It’s constant and accelerating change.

Following hot on the heels of your planning work in the B2B product launch process is the need to get your people sorted.

The fifth B2B product launch process step is to align your people.

After you’ve planned the launch, you should get your protagonists together to review the planning, get their feedback, and make sure they’re comfortable committing to what you’re asking of them and their departments.

For this reason it’s wise to allow a bit of wiggle room time before executing the plan. This enables you to iterate your planning document so that all the key players are happy with the modified version.

Another useful step to build in is the consideration and incorporation of any feedback and experiences from those of your partners and customers who have had access to any prototypes or beta versions of your product. This work may have knock-on effects for your lead times and planning, so you’ll be thanking yourself for building in buffer before you hit the execute button. It’s also a good time to capture agreement from these early adopters to help with marketing endorsements and – in the absence of paying customers for the product – build credibility and confidence for the launch.

So, you’ve done your planning, got it blessed, and profited from the feedback loop on early versions of the product. You’re good to go.

In our third B2B product launch process step, we were busy gathering our requirements, making sure that we had as much information at our disposal for the next stage.

The fourth step in the B2B product launch process step is to do your planning.

Here’s a process that I find works for me:

  • Work backwards from the launch date
  • Figure out the individual tasks that need to be done by each department or function, noting any dependencies, or sequential tasks that cannot be done until another task has been completed
  • Decide when the tasks need to be done by, in other words how many days before launch
  • Assign an individual responsible for delivering each task
  • Calculate how long each task is going to take
  • Make sure that some individuals or functions don’t have a total of days that looks too challenging to fit in before the launch date. If the total number of days is greater than half the available days for a person or team, they might be too stretched to deliver on time, and you may need to look at scaling back their tasks or finding someone else to help out
  • Plot when all the tasks need to start. As each task naturally becomes a line item on a spreadsheet, you can then monitor progress as you go

With your planning done, you can set about getting your people ready to execute, and get into the fifth stage.

In our second B2B product launch process step, we looked at the kick-off call and how the project team members shared their expectations and requirements. Now it’s time to do something with those requirements.

The third step is to gather those requirements.

What is your objective for this project? Sure, you want a successful launch, but you need to get more granular in terms of specific requirements that you can subsequently measure to get a sense of how you did when you come to the review stage. Also, these requirements need to work across your launch team. You’ve already heard a range of opinions in the kick-off call. Now you need to consolidate them into a set that works best for the business and get everyone behind them.

Here are some of the basics you need to think about:

  • What revenues are you looking to achieve from the project? This may already be stated in your business case document. Numbers of customers, partners, average attachment rate – number of products per customer – increase?
  • What kind of a launch do you need? A phased, ‘soft’ launch with an extended beta phase and a gradual expansion of availability across customers, prospect groups, regions and so on? Or perhaps a ‘hard, big bang’ launch, which carries more risk but gives you more awareness and a quicker hit?
  • What use cases or scenarios will your product cater to? What kind of customers or success stories will you use to best endorse the launch?
  • What will the product do? What is the scope of the product?
  • What are the specific requirements that each department or function involved in the product will have to deliver to? Development, testing, marketing, sales, product management, operations, professional services and implementation, support?

Once you’ve defined all your requirements for your product launch, you need to socialise them with the rest of the team, and be prepared for some toing and froing, before you have an agreed set. Then you can set about figuring out how you’re going to meet them, which is the topic of our fourth step.

In our first B2B product launch process step, I recommended you get the fundamental information together and check your facts. Once done, you’re ready for the second step.

This step is to have your kick-off meeting or call. If you’re well organised, it shouldn’t matter if you can’t get people to a physical meeting. A call should be fine.

In this call you need all the major players – or else their delegated representatives – in the product launch to be present. This is where you set your ground rules, make sure expectations are aligned and roles and responsibilities understood. The kick-off is a great opportunity for all those who don’t know each other to get acquainted and understand how their own contribution will butt up to or overlap with the contributions of others.

On this call it’s a good idea for people to share their expectations and their requirements for the project so that everyone is aligned towards the overall objective for the launch – whatever the project team decides that overall objective should be. You can’t do any decent planning without the over-arching objective agreed, so it’s important to agree this before proceeding. This is also an important time for establishing what any dependencies or interdependencies might be for elements in the project. What stages can run in parallel, what have to be sequential, what the rate-determining steps are.

From an interpersonal and cultural perspective, the kick-off is the chance for the project manager of the launch – which might be you – to set the tone for the meetings, how they should be run and what the protocols are for reporting, meeting attendance, escalation procedures and so on.

You can use software or design fancy spreadsheets to help you automate much of the operational stuff, especially with large or comprehensive launches. You still, however, have to get the basics right – the basics I’ve outlined above.

With a good kick-off call under your belt and your objective and requirements defined, you’re all the set for the next stage.

 

Some people have job roles where they’re in a lot of meetings. Typically managers of people have this issue. Back-to-back meetings, or worse still, meetings that over-run and put them behind all day.

I often find myself in a position where I need to create stuff. I need thinking time, planning time and writing time. Meetings are the enemy in this situation. Sure, they have their purpose, and a very useful one at that, when managed properly, but not if I need sustained ‘me time’ to get my work done.

My approach to meetings is under-promise, over-deliver. Ask someone for more time than you need – don’t go mad, it’s a balance between taking their time and taking liberties – and book that time in the calendar. Then, aim to finish the meeting early. 45 minutes is a good length of time to ask for a meeting. Even if you finish on time, in all probability they’ll have a precious quarter-hour before their next commitment.

There are few things better than a meeting finishing early and giving you some of your hour or day back. And you’re grateful to the person who organised or chaired the meeting for that. It shows you that the person values your time and doesn’t waste it.

Were you ever at a school that managed its timetable in 50-minute slots, and started each class at the top of the hour? Those little 10 minutes back every hour are great for getting fiddly stuff out of the way, running quick errands and getting your head right for the next meeting.

Aim to finish your meetings early. Control them so that they do. Tell the other people that you’re done and that you’re giving them back some of their day. They’ll respect you for it and will be more inclined to grant you their time again.

Very little in work is genuinely new and original. The huge majority of it is re-examined, revised, re-worked. A document used as a base for something else, a presentation template where you can borrow the formatting and graphics, a white paper where you can adapt the ideas: it makes sense to do this.

Working from a solid base that has already found acceptance is sensible, a productive use of your time and investment.

That’s not to say that we shouldn’t strive for something that starts from a blank sheet of paper. Sometimes it’s the only way to come up with something that’s fresh, exciting, or game-changing.

But in the day-to-day passage of getting things done, re-work, re-use and recycling is a good thing.

It’s not plagiarism, where you’re passing somebody else’s work as your own and plagiarising their intellectual property. Properly acknowledged, cited or quoted, someone’s work you have built on is generally the better for it.