Browsing Tag

business

Roadmapping: Implementing Strategy

Are you new around here?  Spatially Relevant is about sharing/identifying trends in marketing, branding and how product managers can change a business with technology, such as social media.  Stick around and add the rss feed to your reader or follow on twitter.  Now on to the article.

—-

Roadmaps change and fluctuate based on strategy, capacity and based on what was and what wasn’t delivered, but it is important to know manage your roadmap against the business needs, not the calendar.   To that end, I just took a video on demand session a couple of weeks ago or so in my spare time, but I wanted to get it done since in fact I’m starting a new gig and more education is always a good thing.  So with a little extra time on my calendar lately, I was able to sit through the Pragmatic Roadmapping session which was a very reasonable online course which made me think a bunch about planning and managing successfully towards a strategic initiative.

Roadmaps: The Vision Translator

Everyone wants to be a visionary and create a roadmap isn’t the time for vision – it is time for distillation of the existing strategy goals, plans and vision.    Another way to look at it is sometimes you just need to manage the business to get things done and as product manager with little authority, but all the accountability having an executive approved artifact can be a good tool to get everyone aligned.  Ultimately, The roadmap should connect strategy to execution –  where big ideas meet math, time and priority.    Strategy translated into revenue is the roadmap, revenue goals aligned to delivery time lines are releases and features to drive revenue are sprint, iterations or builds – whatever it is in your software shop.

Release Plans are Roadmap Derivatives

I got to start some release planning at the old gig and realized that it appeared that we jumped from big ideas to features.   In this mode, roadmaps are schedules, not strategic plans or commitments.  Don’t get me wrong, release planning is a vital step in delivering on the strategic goals and visions for the business and is a very exciting time, but it should be how you translate an agree to plan into action.

Roadmaps: Committing to the Business, Committing to the Market and your Customers

Growth is one of the most exciting things to pursue in technology, but requires plans, deliverables, commitments and accountability.   This is where the roadmap fits in.  Many organizations invest significant time and energy into revitalizing their strategy, but often fall back into the quarterly or semi-annual release planning mode and not looking at the deliverables required to position successful growth.  Revenue, dates, systems, people, products and customers are all part of the roadmap development.

The video which Steve presented covers not just delivering features and time lines, but focuses on connecting strategy to project/tactics.  One way to look at a roadmap just might be as a commitment for product managers to the business and a tool for prioritizing delivery.  The roadmap essentially becomes the contract which product managers manage against to ensure they are driving towards the desired goals and deliverables for the business.

If this is of interest to you, you can use the following discount code for $100 off – S06RM09.  I think it was originally god for like 30 days and due to my slacking there is probably only like 7 days left – so get on it!

Overall it was a very productive session on focusing on delivering on the strategic themes for the business…it definitely made me think more about roadmaps than I have in a long time.  Many thank to the folks at Pragmatic Marketing for putting this together and letting me share with y’all a little discount.

Betamax Wins! An interview with Jim Foxworthy

Are you new around here?  Spatially Relevant, not only is about sharing the things we find from cool people, but also sharing/identifying trends in marketing, branding and how product managers can change a business with technology, such as social media.  Stick around and add the rss feed to your reader or follow on twitter.  Now on to the article.


Ok, so those of you around long enough know this isn’t the case with Betamax and we are now all upgrading to that blue thing, but the important part is Beta.    If you have been around product management long enough you know that processes and methodologies come and go, but best practices stay the same.  In technology one of the perennial milestones is going Beta.  While a technical feedback loop, it more so a market feedback loop.   It’s this step in any process where most of us get just a little nervous with the launch process, but hopefully not if you had launch in your mind since concept.  So like most product managers, my technical background and experience historically saw the close of beta and launch as milestones, rather than an ongoing process which started with the market requirements.

After leveraging the folks at Pragmatic Marketing to understand best practices in product management for almost a decade, I’ve come to see launch as an integrated process which parallels most of the development.   So I was glad to hear they were adding dedicated course on launch to the training catalog and was SUPER excited to participate in the beta.

Yup, Pragmatic Marketing is launching a new course on Launch Essentials and I had the opportunity to beta it onsite with the whole team – Product Owners, Technical PM’s, MARCOM and Product Marketing.   During the day I was impressed not just by the content, but the beta engagement process.  By being part of the process I was able to learn new things and share feedback with the instructor, David Daniels, and Graham  Joyce which is the goal of any beta, but the structure and measurement of the feedback is integrated into the process real time for the Pragmatic team.   Just as with any beta process, the team was looking to ensure as they launched a “product” to market it which actually meets the needs of their target market.   During the 1 day workshop we addressed the typical problems/pitfalls in launching a technology product to market profitably and the team challenged the pragmatic folks on how to ensure our Agile processes and launch methodologies were synched from concept to launch.

So with a little extra access to the team, I decided to see if I could ask some questions of Jim Foxworthy, the VP of Product Marketing at Pragmatic Marketing and Jim was kind enough to participate, as you can see by the title of the post.    The goal of the interview below is to get some insights on their beta process and the types of folks they have in their business.    I have similar interviews of two other pragmatic folks (David Daniels & Steve Johnson) to read which validate the varied backgrounds and common view of successful product managers which are echoed below by Jim’s answers.

Many thanks to Jim and best of luck to the team on the launch of the new course, with the standardize beta process, measurement and market engagement I’m confident it will be a success!

Q. What Roles have you had in the industry prior to joining Pragmatic Marketing?

I started in technology in 1975, so the ‘roles’ list would be a bit boring and long! But suffice to say that I worked in IT shops until 1983 doing operations and some development, then independent vendors until 2001, then joined Pragmatic Marketing as an instructor. During my years with vendors, I did customer support, client training, sales, and product management.

By the way, not that you asked, but while carrying a sales quota was not the easiest gig for me, the experience paid big dividends. On occasion we get a laugh at the expense of our sales brethren, but knowing what it takes to close business made me a much more effective product manager.

In 2002, while continuing to teach for Pragmatic Marketing, I started a consulting practice focused exclusively on implementation of the Pragmatic Marketing Framework. Over the following five years I worked on nearly 100 implementations.

Q. As you were with the other companies did you use the framework in other roles?

I was a student the first time Pragmatic Marketing offered the “Practical Product Management” seminar in 1993. I had both successful and unsuccessful implementations of the Pragmatic Marketing Framework between 1993 and 2001. I prefer to think of my mistakes as ‘opportunities to learn’, but some of them were unpleasant!

Q. I recently participated in a Beta process with you and the team and it appears that you not only eat your own dog food, but have a tightly defined beta program, expectations of the participants and adjusting the product in response.  How is this different than you have worked beta programs previously?

Thanks for the compliment! Being the product manager here at Pragmatic Marketing doesn’t give me much latitude to ‘stray’ from what we teach. The other instructors are NOT shy when I do (smile)!

In many ways our Beta process is not that different from programs I have run in the past. Our ‘product’ is our seminar, and the source code is in (believe it or not!) MS-PowerPoint. So, when the ‘code’ begins to look pretty close to the requirements and the positioning (we do those, too) then we know it is time to get some market validation. Beta testing gives us that, plus one more thing that we cannot duplicate in the ‘development lab’ — real teaching time. There are some things about the delivery of seminars that you can -only- learn on your feet, working with a live audience.

Q. How are the emerging development agile methodologies impacting the framework or the way PM’s need to look at the market?

Agile development methodologies are having a big impact on product managers! New artifacts and job titles are emerging that can be confusing, and there is an enormous about of pressure to spend more and more time with development. Yet the need to discover and validate market problems has NOT changed. Pragmatic Marketing recently launched a new seminar titled, “Living in an Agile World” to address these very issues. (If I had my go-to-market hat on, then I would write) For more information, please go to www.pragmaticmarketing.com.

Don’t be a product management victim.

Josh has some good quotes and some good ideas. Good communication, cross functional engagement and clear plans are essential. The presentation conceptually represents the type of content you will find on his blog, A Random Jog, check him out.

I hope to get back to writing in the next week or so, just way too busy with travel and stuff. Excited about being in Chicago for the weekend, so those of you who will be at SOBCon. Cheers!

~jon