The Thought Process behind Blueprint – Part 1

Part 1

Welcome to the first in a series of posts that help explain the thinking behind the Blueprint platform from Purmea.

While marketers wisely advise staying away from complex pitches and taglines as they can just confuse potential customers, there is value in understanding what underlying complexities and structures drove the evolution of a system.

Conversely, while loyal and passionate users of a technology want to understand the next features, there’s value in stepping back in order understand what drove the architecture.

So while the problem > solution > benefits message helps set the value proposition and the product roadmap give a sense of what’s next, both are lacking when it comes to setting expectations and explaining a vision.

I recently watched the September 2016 Apple keynote introducing the iPhone 7. Apple has always done a great job of drawing you into their product lines with the story of what you get (the marketing), and they have also done an amazing job of covering the features for their fans (the product), but even in this last keynote, Phil took time out to explain the vision behind why they removed the analog audio jack from the phone. Neither marketing nor product features alone could satisfy the need to present a direction. He had to create a compelling vision for us, the audience. And for my money, I thought he did a good job.

So if you want to understand the marketing for Blueprint, simply go to the Purmea home page. If you want to see the features that have recently been released or are upcoming, go to the Roadmap page; but this series of posts offer insights into the thinking behind the whole product.

To start, there are two prime directives, if you will, that drive almost all of the features and construction behind Blueprint.

Coherence – Describe what’s valuable and what success looks like and then you can see if where you’re investing your time and money matches that.

Alignment – Work with others to share your desired outcomes, approaches and milestones as well as your projects to see if everyone agrees on the basic direction and priorities.

If you’re an individual who values those two aspects and are a leader in an organization with either a budget and/or a team, you will likely find value in Blueprint.

In the next posts, I will delve more into the specific thinking behind particular aspects of Blueprint and how they map to the above prime directives.