Joel Liu's Library tagged → View Popular, Search in Google
-
So true. I think the sign of a great PM is the ability to see all the imperfections but the self-control to focus on the things that matter and to de-prioritize the things that don't.
It's easy to make a list of everything wrong with your product and spend eternity trying to fix it all. It's harder to reconcile imperfection with the reality of limited resources and business objectives.
-
We designed our product so that every class is recorded just easily as one is. We built a product that people use every day and that our sales people can feel good about selling to our customers. I'm not sure the salesperson who sold that installation would feel very good about returning to that school. We have no interest in building a product that isn't being used every day all school year long.
-
This is tangentally related, but I'm going to break my contract with Verizon after buying a Motorola Devour in March. I believe that Motorola and VZW have broken an implied promise to support my Android phone through the update cycle; it shipped with 1.6 and it appears that the powers that be have decided that it's not worthy of the engineering resources to get it up to 2.2, so it'll be at 1.6 forever.
I'm sorry, but a three-month old phone should not be obsolete. If I get a iPhone 4, I have every confidence that Apple will make every effort to ensure that subsequent iOS upgrades work on my phone until there's a legitimate technical reason to exclude it, not some bullshit profit/loss maximization algorithm.
The Android ecosystem will remain fragmented because every single phone+manufacturer+carrier combination requires a decision and engineering resources to upgrade. I could never recommend an Android phone to anyone but the anti-Apple hordes.
Fun is the easiest way to change people's behaviour!
-
Tip1: Start from Epicenter of the idea, product
Epicenter is the core and what a product stands for. Stick to/start with what product stands for and only build features that defines you and your business. Build half the products that you want to build, but not half assed product; cutting out what is merely good, only keep the core and the best. -
Building a product for a new business should be the same way, instead of setting up long term goals, 3 months long feature sets plan, breaking them down to mini-sets, weekly feature-sets-milestone will make you aware of your progress more, bringing more motivation and fuel to keep going strong. This is how I am building mine now.
- 1 more annotation(s)...
1. Control the variable, reduce risk.
2. Tick = Big version, Tock: Continue improvement.
-
Tick-tock in action
Year 1: First the "Tick"
Intel delivers new silicon process technology, dramatically increasing transistor density while enhancing performance and energy efficiency within a smaller, more refined version of our existing microarchitecture.
Year 2: Then the "Tock"
Intel delivers entirely new processor microarchitecture to optimize the value of the increased number of transistors and technology updates now available.
in list: Product managment
-
This being HN, let's talk about software.
I have seen people very wrong-headedly trying to apply rules to all employees because of one misbehaving person, under the misguided notion that this is somehow "fair". For example, a long time ago there was a person in the admin group that was basically a slacker - came in late, left early and didn't work very hard. Management got really annoyed by this and made a "Everybody in by 9am OR ELSE, no exceptions" rule. Well you can imagine how that went down will all us geeks who were slaving 14 hours a day till the witching hour to fix problems. They managed to piss off the most productive people in the building, instead of standing up to one person and saying "you will be in by 9am, because that is when your manager needs you, and if you're not, you will be fired".
So, unless you are managing an organisation that is so large, and you trust your middle management so little, that you can not address problems on a case-by-case basis, then stay away from sweeping rules. I'm with the OP on this one.
in list: Product managment
-
4. Force business to iterate in design, not in development
There’s nothing a developer hates more then spending months on something that once the business guys see it they realize they want to do something else. I won’t hand anything off to the developers until I have thought it through and iterated through it with the business guys as much as humanly possible. There are many decisions that can be made off of drawings rather than programming it. And business will quickly realize that getting the designers to change their designs is a thousand times cheaper than paying expensive developers.
-
There’s nothing a developer hates more then spending months on something that once the business guys see it they realize they want to do something else. I won’t hand anything off to the developers until I have thought it through and iterated through it with the business guys as much as humanly possible. There are many decisions that can be made off of drawings rather than programming it. And business will quickly realize that getting the designers to change their designs is a thousand times cheaper than paying expensive developers.
-
Steve Jobs is the ultimate visionary. He has a vision, he implements it, and the world pays him tens of billions of dollars for it. He doesn’t ask customers what they want because they would ask for a faster horse, not a car. He knows what customers want before the customers do. He is the quintessent entrepreneur — the ideal that every founder strives to become.
-
Steve Jobs: “Originally, we weren’t exactly sure how to market the Touch. Was it an iPhone without the phone? Was it a pocket computer? What happened was, what customers told us was, they started to see it as a game machine. Because a lot of the games were free on the store. Customers started to tell us, “You don’t know what you’ve got here — it’s a great game machine, with the multitouch screen, the accelerometer, and so on.”
“We started to market it that way, and it just took off. And now what we really see is it’s the lowest-cost way to the App Store, and that’s the big draw. So what we were focused on is just reducing the price to $199. We don’t need to add new stuff — we need to get the price down where everyone can afford it.”
- 3 more annotation(s)...
-
The purpose of the MVP is to answer your most pressing question, to validate your most pressing business assumption. To create an MVP work backwards from your question, not forwards from a feature list. Invest as little as possible to answer the question because after this there will be another question and another and you’ll need enough money to answer them all.
-
There’s nothing wrong with guessing, dreaming, or predicting, but it’s not planning. Planning’s too definite a term for most things. We often use planning when we really mean guessing. And what we call it has a lot to do with how we think about it, do about it, and devote to it. I think companies often over think, over do, and over devote to planning.
-
Planning just leads to a work-in-progress plan whose success hinges on planning being a frequent activity and constantly changing. Planning is absolutely integral to success, whether you call it guessing or whatever (although the word dreaming seems a bit misleading).
- 3 more annotation(s)...
-
balsamiq is great for ui mockup. Other than that I agree with habs, paper works. Although i have recently started using Microsoft One Note 2007. It makes for great brainstorming / idea throwing / white boarding.
-
I like to use mindmaps for planning and concept work like this.
Freemind is a good open source mindmap editor for the desktop.
Or you could try my online, browser-based mindmap app. http://thoughtmuse.com ;)
- 1 more annotation(s)...
Selected Tags
Related Tags
Top Contributors
Groups interested in pm
-
Technology Leg
Resources listed in Technolo...
Items: 28 | Visits: 12
Created by: UTSC eScholarship Unit
-
Online Mentoring
a collection of links derive...
Items: 4 | Visits: 41
Created by: Paul Beaufait
-
PM
Items: 15 | Visits: 15
Created by: snulyk snul
Diigo is about better ways to research, share and collaborate on information. Learn more »
Join Diigo
