From &quot;quick win&quot; to &quot;permanent loss&quot;
Autor: Eduardo Rodrigues | Publicado: 2012-11-29T11:45:00-02:00


&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Para ler este post em português clique AQUI

A few days ago, a friend of mine contacted me asking for my opinion about the overall strategy of a Business Intelligence (BI) project she was working on: the idea was to deliver the entire front-end presentation layer (reports, dashboards, etc.) and only then start working on the Data Warehouse layer meaning the whole modeling, data structuring and ETL (Extraction, Transformation and Load). According to her&nbsp;description they could not even tell all data sources which were needed to deliver the already&nbsp;committed front-end layer.&nbsp;




I believe most of us have already experienced a similar situation. I have seen it under many names and concepts, but usually we can simplify it by calling it a "quick win". By "quick win" we usually mean something (a part of a project, a specific&nbsp;functionality&nbsp;or something alike) that can be delivered really fast (in&nbsp;comparison&nbsp;to the whole deliverable), in a reasonable cost (also compared with the whole deliverable) and mainly can deliver a high value added. In an ideal world, that would mean to expend 20% of the resources that will bring 80% of the value added (in a simplified Pareto analysis).&nbsp;



It should be mentioned, that while running for the "quick win", it is possible that some&nbsp;governance&nbsp;rules or&nbsp;best practices guidelines are overlooked in order to&nbsp;reduce&nbsp;furthermore the amount of resources invested. Clearly it can only be done when&nbsp;previously&nbsp;agreed with all stakeholders and under the strict commitment to fulfill all the necessary requirements when implementing the remaining project.&nbsp;



Needless to say that the advent of the "quick win" bears no roots on technical grounds. Out of my experience, if you ask a&nbsp;technician if he/she would like to deliver "the perfect solution at any cost" or a "usable solution at a very low cost" he/she would&nbsp;gladly&nbsp;explain that although the low cost solution can be used, as such, it has an enormous list of disadvantages and risks that must be taking into consideration.&nbsp;



So, in order to build up a solution that actually can be sold - a very important perspective of a consultancy company by the way, technicians all over the world (myself included) depend on our&nbsp;marketing, sales and project managers colleagues. Who were brilliant on bringing up to the business solutions that fits&nbsp;both&nbsp;the customers needs and the standard of delivering the best possible solution by introducing&nbsp;the phasing approaching,&nbsp;prioritization&nbsp;of&nbsp;deliverable&nbsp;and, of course, "quick wins". &nbsp;&nbsp;



To say it straight away: I support the "quick win" approach as a tool to make projects possible and viable. I believe that if we can find the right "thing" (be it a report, a process, a dashboard, workflow, etc.) that can really tip the scale to our customers, we should get it done as soon as possible in order to guarantee a fast ROI (Return Over Investment) and moreover the competitive advantage our customers are always looking for.&nbsp;



However, I disagree with the approach, sometimes "quick and dirty", some solutions are sold and delivered. I disagree with the idea of&nbsp;delivering&nbsp;everything as a "quick win" or a "productive prototype" as I have seen several times. I would&nbsp;encourage&nbsp;all those willing to use the "quick win" approach to follow a very simple checklist:



understand your client environment, its problems, opportunities and challenges;
propose a complete and sustainable solution;
highlight the "things" that could be done with a small amount of resources (time, money and people) and potentially can bring a huge benefit (productivity, profit,&nbsp;efficiency, etc.);
if needed - in order to make the project viable - create a four hands&nbsp;road-map&nbsp;or a program in order to apply the phasing approach.


With the simple checklist&nbsp;above, you will make sure not to overlook the big picture.



Regards,

_______



Eduardo Rodrigues is a Business Intelligence professional for 8 years, he has worked as client, entrepreneur, speaker, consultant, solution architect and project manager. Married with two children, he is also author of a poetry book called “Poemas de Botequim”. LinkedIn profile&nbsp;http://br.linkedin.com/in/rodrigueseduardo. Follow him on Twitter&nbsp;https://twitter.com/edur0dr1gue5