This days I participate to a presentation of a product. The idea of the product was great, I think that they will have a lot of success in the future.Being a technical presentation, the presentation was held by one of the developers of the team. From this point of view this was great, because the audience was developers and other technical person. He could respond to a lot of question related to architecture, scalability, protocol that were used, base concept and so on.
Until….
Someone asked about something related to business idea and what kind of problem this application will solved….
In that moment our developer stopped……..
He could not give an answer….
And…he sad…
I’m a technical person, is not my business to know the business of the application!
In that moment I freeze. How the hell you can develop an application without understand the business? This is one of the biggest mistakes that can be done by a team member – refuse to understand the business of the application. Before thinking to a solution it is a have to understand the business of the application itself.
How you can resolve a problem without understanding the problem itself?
Being a monkey, a monkey with keyboard is great for a monkey. But when you need to solve a problem and give a solution, being a monkey with keyboard is not enough… This is how you end up with an airplane when a customers wanted a car.
0 comments:
Post a Comment