Shyam's Slide Share Presentations


This article/post is from a third party website. The views expressed are that of the author. We at Capacity Building & Development may not necessarily subscribe to it completely. The relevance & applicability of the content is limited to certain geographic zones.It is not universal.


Monday, August 21, 2017

The Process vs. The Product 08-21

Shyam's take on The Process vs The Product...

The ultimate aim of any product or service should be to create that MOJO effect for the customer. Even a feeling that says, "Why didn't someone come out with this earlier". But you can't do this without a process, and I am not referring to the processes required to create a product.

The processes required to create a product are of course are an absolute inevitable. The confidence to create a MOJO effect stems from the quality of the product. However you need a process to create the MOJO effect, and there is no standard procedure about it.

Every time you need to create a standard process to create new standards in customer engagement. You need a promotional process that can create a benchmark in the minds of the customers about quality, utility, and the cost effectiveness of the product and also the one that elevates the customer esteem for the organization and its other products.

The process should make the product strong enough in customer perception, to enable other equally good but poorly promoted, products of the organization to piggy ride on the new esteem acquired through this product.

Now the article...

We work in an industry that glorifies the process of everything we build.

We are obsessed with roadmaps, methodologies, acronyms, and productivity tools. This shared language gives us a sense of belonging and makes us feel like we are in fact product people.
Process is important in life. And we should seek to build high quality products with focus and efficiency. I would never argue against that.

Product Managers and Product Designers glorify our process for building products on Twitter, podcasts, and at conferences — but we should remember something important.
Customers don’t actually care about how we build our products, or our process.
Customers do not care about our Slack debates, our Jira tickets, or the compromises we make to our roadmap along the way.

Customers only care about how our products feel in their hands, and nothing else.
That moment when customers first open our apps and escape their reality for a few minutes as they discover something new — that is the moment that matters if you build products.
We need to focus less on glorifying our process for everything we ‘product people’ do and focus more on what actually matters.

What matters is that we build products that make customers smile and realize something new about themselves.

What matters is that we build products that make life more fulfilling for billions of people by giving them access to education and new ideas.

What matters is that we build products which make customers say: I honestly can’t imagine my life before I downloaded that app.

We Product Managers spend our days writing specs, filing Jira tickets, and editing roadmaps. Process. Process. Process.

What else could we have created instead of that perfect Gantt chart?

Are there easy wins in our production apps that we could have discovered instead of seeking the perfect process?

Can we think less about our perfect Product Manager workflows and think more about simplifying our products?

Our job is to delight customers through the projects we build. Process is important, but do not forget that customers judge us on one thing. 

No comments:

Post a Comment