The interception point between UX Tech Business
- They interact with a lot of people
- Get collaboration from engineers and designers
- Communications hub, organiser and enabler for everyone else
- Person that stops sales and legal from emailing developer lol
- Responsible for the success of the product
What is a product?
It could be anything...
Product managers are in charge of sections of a product.
PMs can be split up on different aspects of the product
Types of product managers
- Internal PMs (small scale)
- Great intro role
- integrate with other systems
- project management
- Less risk
- small number of users
- Business to business PMs (SAAS PMs) (e.g zoho, workforce)
- Good intro role
- Small number of users
- Flexible and creativity
- Priorities weighted by money
- Tighter deadlines
- One or very few platforms
- Business to Consumer PMs (product is for other consumers)
- Uncertainty
- Pressure
- Millions of users
- Can lose company money
- On several platforms (web iOS Android)
Stakeholders
- Users
- Executives
- Marketing
- Legal
Product and project management
Product managers are responsible for accomplishing a metric goal through any method they choose with their teams, and Project managers are responsible for accomplishing a set project with thin resources and time constraint
The Product Lifecycle (Framework)
- Introduction
- Product first introduction to the market
- Little to no competition
- Typically loses money
- Early adopters
- Growth
- Accepted by marketplace
- Sales rise
- Start improving product
- Few competitors
- Maturity
- Sales peak
- Competitors enter market
- Decline
- Sales diminish
- Products phased out
- Deemed old/irrelevant
Product Development Process
- Conceive
- Collect user problems
- Brainstorm solutions
- Select focus areas
- Ideas come from employers/owners of the company
- Plan
- Market research
- Customer interview
- Roadmap
- Develop
- Make timeline
- Features
- Developers come in
- Requirements are set
- Iterate
- finish MVP or prototype
- feedback from users
- check if idea is same as product
- Roll out test feedback Alpha/Beta testing
- Launch
- Work with marketing, legal, PR & sales team
- Steady state
- Collect user data
- continuous sales and marketing
- Maintain or Kill
- Use data collected to know if product is still up
- How much money spent to maintain it
- Is th product paying for itself
- Check ROI
- Company gaol/direction may change
- Activate operation SUNSETTING
LEAN vs AGILE
LEAN (Lecture 22)
Revolves around cutting all of the unnecessary work or efforts until
you're absolutely sure you need to do it.
- Do as much as you can in the begining to save resources
- Experiment. listen to customer feedback, favour iterative design
- Don't build anything until you know there's interest in it
AGILE
Applying the LEAN mindset to software development
- Applying the learning mindset to development
- Eliminating wasted time and resources by developing the product iteratively and incrementally.
- Grouping things into small batches and completing them one by one
Share with your friends: |
