You know you are doing it wrong when …

  • You focus on things that are not part of the core product
  • You think that you are smarter than the competition
  • You think technology is the key driver
  • You make assumptions and stick to them over time
  • You think marketing can sell any product
  • the items in the backlog have nothing to do with the user experience
  • you create a strategy that is more of a vision
  • you are spending more than 10% of your working time on meetings
  • 50% or more of your workload is action points from meetings
  • the best brains in the company eat Prozac
  • the best developers in the company are doing UML
  • your boss says “I have not had the time to read that e-mail yet”
  • When you have a strategy that says something like “We are going to be the new Apple”
  • you work according to the waterfall-model and call it agile product development
  • you think that enterprise solutions is a must have in order to serve all your customers
  • you hear the word ITIL
  • someone thinks that abstraction and not function has critical impact on business
  • someone suggests a new meeting in the matter
  • you think someone else should decide in the matter
  • reorganizations is more common than company beers
  • you have two (or more) bosses on the same position
  • there are only men (who only eat meat) at the top of the ladder of your company
  • you think that it is better to build it yourself
  • you think that it is better to rebuild than to tune
  • you think that your success is a strike of genius rather than a lucky shot
  • when the CC:field is used in more than 50% of your inbox e-mails
  • when you have architects
  • when you have usability experts
  • when you have middle management
  • when you feel stuck because of salary and benefits
  • when you are building an enabling platform that will solve all your problems
  • it is more important who is in charge of something than what gets done
  • you have three levels of the organizational hierarchy below you …. and three above
  • people are leaving without knowing what to do later
  • you discuss things longer than implementing them
  • there are people walking around the office that look like movie stars
  • most of the people working at your company think that they should not have to do any real job and get their hands dirty
  • you buy new project tracking software and think that you have found the key to success
  • when someone from payroll sends their first mail with Comic-Sans and two or more clip arts pictures
  • when you get saluted for a good year and get a salary increase, even though you obviously do not deserve it
  • you have a group that works with R&D and no one knows what they actually do
  • you are part of a working group that forces you to dedicate 25% of your time because you are one of the big thinkers in the company
  • you have multiple offices and people would rather fly to the other office than setting up a video conference
  • middle management can’t say anything without adding some bosses name into the conversation
  • you feel that you are going in the wrong direction professionally and personally and you have an annoying feeling that it probably has a lot to do with your current job
  • you have more than one Lead Developer for a product
  • you think you are building stuff that another department think they build
  • you don’t get angry anymore over things at work
  • you feel like it is impossible to change something
  • you feel that the good old days were way better

Evolutionary or Revolutionary Product Development?

I read an interesting article the other day on how Facebook scale and manage to actually serve 300 million users with immediate updates made to the network of friends. One thing that strike me when it comes to the article is the part where they discuss the introduction of the “Like”-feature. The discussion before the introduction was wether or not it would effect the use of commenting. It did not, it actually added an extra layer of customer interaction to the product, a feature that quickly became very popular. What is most interesting I think is the evolutionary approach to the user experience such a feature is. When you finally have switched your product development to be user experience driven, you also have to make a choice whether or not your changes to the product will take the revolutionary or the evolutionary approach.

A lot of people will always argue that in order to reach the high set goals you have, you have to take on an revolutionary approach to your product development, and others will say that taking on the revolutionary approach to product development is building a product based on facts and requirements that are not the actual facts and requirements that are present when the revolutionary approach are implemented and put into production.

In this post I will discuss and share my ideas on different strategies and approaches to your product development.

Last Weeks Tweets from FrontendBook – 2009-10-18

Last Weeks Tweets from FrontendBook – 2009-10-11

Last Weeks Tweets from FrontendBook – 2009-10-04