Monthly Archives: October 2015

Three Agile Tools to create winning teams

Do you want to create winning teams?  Or improve already effective teams?  Agile can help – regardless of what department you are in.  As background, Agile is a software development methodology that uses practical tools and concepts to empower people to be more productive. Here are three tools that you can start using immediately to enhance teamwork and trust in your organization.

Working Agreement

What is it?

winningteams1A working agreement is a document of the values and behaviors that your team defines for how they will work together. It is powerful because it is crafted by the team, for the team (not by management).  It facilitates great discussion about what will work for all team members. It could address topics such as after-hours availability, meeting etiquette, team member attitudes on interruptions, philosophical positions on accountability and more.

How to get started:

The easiest way to introduce a working agreement at the office is before a long meeting. The meeting could be a few hours or a few days, but long durations tend to bring out the worst in all of us. Ask for five minutes at the start of the meeting to document a working agreement. Ask everyone to define the appropriate behaviors for the meeting. You may have to prompt the group with provocative questions like “Are smartphones allowed? Who is taking meeting minutes? When are break times? If everyone is not back after a break, does the meeting commence, or do we wait?” With a little prompting, a healthy discussion should take place. Write down the results of the discussion and keep the working agreement displayed throughout the meeting.  If anyone violates a tenet of the working agreement, any team member can gently point out the discrepancy and the meeting can continue. This simple introduction to working agreements will allow people to become familiar with the practice and then you can apply it more broadly to project teams.

Launch a Product – Step 5: Communication

This is the final installment in our blog series “what does it take to launch a product?” If you are interested in the previous posts, we covered Product DefinitionPricingSales Announce2Enablement and Making Hard Choices.  This blog will highlight the communication plan that is required with a product launch. Like many elements of Product Management, it requires more thought and care than might initially be expected.

Here are some tips and tricks regarding communication:

Involve Marketing

If you have a Marketing department that is separate from Product Management, include them in a discussion about launch communication. We all have our skill sets and you want the best players in the right positions. Many product managers are excellent marketers and writers, but they may not have the depth of expertise and relationships that your Marketing team does.  This is an opportunity for close collaboration.

Identify your audiences

You may have several “masters” to serve and they may need to be communicated to very differently. Internally, you have to think about your sales force, executive team, customer service representatives and other company employees. Externally, you have to consider existing customers, prospects, the media, Analyst firms and possibly investors or shareholders. Each audience may need a slightly different message so it is prudent to think through this ahead of time so you aren’t left scrambling right before launch.  Also, some audiences can promote your message so you want to get to them early in the process.

Determine appropriate amount of communication

How much is too much or not enough? Communication can be tricky because you don’t want to over-message something that is small, thus diluting your Marketing credibility. Nor do you want to under-message something big and miss a potential opportunity.

We solved this, like many other companies by creating Launch Levels.  An “A” launch is a big deal – Press Release, videos, micro-site, sales training, etc.  In order to qualify as an “A” launch, it has to be a brand new product or a significant enhancement that will drive revenue.  Depending on your innovation cycle, you may only have one or two “A” launches per year.

A “B” launch is less impactful; it might be only available to existing customers, or it might be an inexpensive add-on that won’t drive significant revenue, or it might be a version 1 product that you are testing on a smaller target market before making a big splash. “B” launches will have fewer marketing assets and activities than an “A” launch but still require thoughtful consideration of content, audience and timing.

“C” launches are more like product enhancements.  You definitely want to get the word out but it isn’t worthy of an Analyst Briefing or new website.

The way we manage the different launch levels is to have a Launch checklist and whether a task is required, optional or ‘as needed’ varies by the launch level.  For example, in our company, a social media campaign plan is required for an “A” launch, ‘as needed’ for a “B” launch and not applicable for a “C” launch.

Have a plan

Even if your organization isn’t mature enough or big enough to have a Marketing department or need the sophistication of launches levels, take the time to craft a communication plan.  It is important to let the world – or at least your sales people and prospects – know about this great new offering.  If you aren’t purposeful about it, or you slap something together at the last minute, it can devalue the product and no one benefits from that!

Launching a product is a highly orchestrated effort that requires thought, planning and follow-through to be successful, but when it is successful, it is a great feeling to see your “baby” hit the market and start generating sales.  There is such a sense of pride and accomplishment that comes from it.  I hope every reader gets to experience that feeling.  Happy launching!

 

Originally posted on a now defunct site on 4/16/13

Image source: http://www.powerelectronicsworld.net/article/0/79963-gigoptix-producing-gaas-e-band-pa-chipsets-in-volume.html