0

Where does your communication roadmap lead?

8739599312_106d291dc6

Communication is one of those things we all know is important. No matter if you are a manager or individual contributor we all must communicate daily. Communication is easy but good communication is tough. What is more difficult is there is no right way to communicate with everyone.

People are different and communication styles are different. Some people prefer direct, in-person communication while others prefer indirect, text message communication. How often do you tell others how you prefer to communicate or ask others how they like to be communicated with?

You can be the person that is a take it or leave it communication style or you can adapt to others and meet them halfway. The more you improve your communication with others the more your success will increase.

So next time you have a new employee, new manager, new friend, or new relationship, start out and ask her for her communication roadmap and provide her yours. This communication roadmap should indicate things like:

  1. Communication style: There are different communication styles. Some people prefer the direct and short style of communication. Not everyone can take being direct and having short communications with some people will make them jump to conclusions that you are unhappy with them. Others prefer the drawn out, beat-around-the-bush style. Whatever a person’s style is try to adapt your communication to it and watch how it pays off.
  2. Communication format: Communication can come in many different forms. I am a face-to-face communicator or at worse on the phone. Sure I respond to emails and voicemails but it is not my preferred format. Knowing the preferred format of people you frequently communicate and trying to engage in that format as it makes sense will help you be more successful in your communications.
  3. Communication frequency: People need different levels of communication frequency. Some people talking with them once a week is plenty while others need to communicate twice a day. Some of the communication frequency is certainly job dependent but much of it is a communication preference.
  4. Communication pet peeves: Some things just piss us off. Letting people know those pet peeves helps people not fall into those communication pitfalls.

Having the communication roadmap for your colleagues, friends, employees, relationships, and manager and providing them your communication roadmap will increase your communication effectiveness. Once you have that roadmap then utilizing it to effectively engage with others will increase your chances for success.

Have an awesome week and remember to do something today to supercharge your success.

As always appreciate your feedback, emails, comments, likes, and re-tweets!

photo credit: w20 – Paul Meyer via photopin (license)

About WorkLearnPlay: WorkLearnPlay.com is about helping information workers live better lives and supercharge their success in the workplace. Please let me know how I can continue to make this site better and help you and others supercharge your success.

0

It is all about the product roadmap

7968397210_064214638c

As organizations focus more on agile development there is an ongoing discussion of product roadmaps and their purpose. Some believe that truly agile teams developing software products don’t need roadmaps. Others have dozens of product roadmaps for the same products and on a weekly basis customize their roadmap for customers and prospects. Then of course there is the rest of the world where there are hardware and service products.

Needless to say product professionals are not happy with their roadmaps. This disappointment is for good reason since most of the time roadmaps are done poorly and done in a manner that does not have a clear purpose. They are less visionary and more instructional.

Product roadmap frustration is often attributed to the mixed purpose and expectations of roadmaps. Roadmaps are used to:

  • Drive more existing customer sales or new customer acquisition by sales;
  • Gain funding for teams and products by executives;
  • Drive cross-team communication tool by project managers;
  • Drive to calm customer frustration by customer service;
  • Gain startup funding by CEO’s and CFO’s;
  • Drive cohesive engineering by development managers.

These are all valid uses of a product roadmap. However, maintaining dozens of product roadmaps is challenging and time consuming and results in wasted effort.

There are many different theories on product roadmaps. My belief is that it is best to keep roadmaps simple and there should be: 1) a visionary roadmap that is used to tell the high level product vision and this can be used by executives, sales, and others; and 2) a detailed roadmap that is a communicative tool to provide precise detail on items being released, timing, and launch information and this can be used by sales, customer service reps, and others to help provide that detail. These roadmaps should be updated together and reviewed at least quarterly.

Some people believe in having external and internal versions of the roadmap. I am a believer in not doing this as it again complicates things. You should be of the belief that your product roadmap is something that will be seen by competitors and this should not scare you but instead scare your competitors.

Visionary Roadmap: The visionary product roadmap should provide the following insights:

  • High-level product vision and value: This is not a one-line mission statement but should concisely state the product status and vision. Think product elevator pitch here.
  • Key product differentiations: This should focus on the key places where your product is differentiated from competitors either positively or negatively. While you certainly do not show how you underperform your competitor but ideally you either take it and address as future enhancement.
  • Upcoming key product advancements: This item should focus on key product enhancements being implemented. The enhancements should flow together with the product vision and clearly align.

Detailed Roadmap: The detailed product roadmap should communicate the same information as the visionary roadmap above but also provide:

  • Product release detail: Provide detailed information of upcoming releases and how they provide value.
  • Product launch: Provide detail about upcoming product launches and information about customer rollout and support.
  • Technology detail: Provide detailed information related to technology and platform.

The creation of product roadmaps not only requires careful written language and accompanying graphics but also requires honesty and provides real expectations that you and your team should believe in delivering upon. My belief is that product roadmaps should be anywhere from 2 to 3 years in length generally. Although it is not uncommon in some industries where product investment is extremely capital intensive to require 5 year or longer roadmaps.

Take this advice to heart and update your product roadmaps today and consolidate as appropriate. Understand that a great product roadmap is like a fine painting that you get the benefit of updating. Most of all use your roadmap to be visionary and communicate between your internal stakeholders and external customers.

Have an awesome week and remember to do something today to supercharge your success.

As always appreciate your feedback, emails, comments, likes, and re-tweets!

photo credit: New York Metro NY-NJ 1950 via photopin (license)