Please enable JavaScript.
Coggle requires JavaScript to display documents.
Building a Product Mindset, Understanding the customer need, MINDSET…
Building a Product Mindset
What is Product Mindset to me?
Ownership and accountability of my modules
Developing the confidence that modules are in safe hands.
To be able to provide quick POC's about a requested feature
Interacting with Systems & Feature Owner to derive my requirements
To understand the internal workings of my module at the deepest level
Thinking of the system from a customers point of view
putting in efforts to achieve the common goal of building an autonomous vehicle
accountability for complete product rather than just the module we are responsible for
Why do we need a Product Mindset?
There is always scope to make the product better
To understand how we contribute to the end product.
To focus on outcome
To bring the good product to the market
To keep our strategic importance as a captive unit
To give vehcile the right direction (Lane)
product mindset will help us to synchronize the use case we are trying to solve
To innovate
Who will be benefitted?
Customers and Company
Self benefit
First you have to see that you are getting something out of it. Once your needs are satisfied, you can expand the circle - your team, the next team and so on
Good Product impact the whole industry
Everyone
How to bring a Product Mindset in my Module?
get a feel for how it all fits into the big picture
know the limitations/ conditions where it could fail and when these could occur
Giving presentations and doing Q&A on different module topics
Re implement a difficult sections of the code in a scripting language for future referance
If a module is transitioned to me from someone else, be thorough with the design documents in EA
By adding related functionality in my module, test it thoroughly that can improve it
Ask why each thing is done the way its done
clear understanding from module to feature
Strive to understand the difficult sections of the module
If something is being done repeatedly, automate it
Try lot of things and fail but don't fail to try.
Where can we apply this mindest?
Understanding our next Level car what can be the different feature and how my module will behave or contribute
In each small process we follow and meetings we attend
Strive to understand the inputs of my module and connect with the developer and exchange my understandings
try to make your work relevant to your life - see how your work can be translated into solving another entirely different problem
Transitions involve change that requires adaptation
Understanding the customer need
To provide the reliable output to user modules
trying to understand all possible real life scenarios and build the functionality.
MINDSET CHANGE
To take the product to be the top notch in the industry