Example Reflection – Visualization

Challenge

I was working as an Inventory Analyst in the Logistics Department of a natural gas distribution  company, and together with my boss, we were designing a project that intended to replace our  current inventory management system (which was based on the use of spreadsheets) for the  MRP (Materials Requirement Planning) module that was included in our SAP ERP system, but  has never been used before. After doing some analysis, we concluded that it would allow us to  enhance our materials requirement planification time and precision. However, we had to  convince our manager about that.

Selection

In order to efficiently communicate our idea, I selected the Visualization tool (though in that  time I was not aware of it as a Design Thinking tool) to convey a clear understanding of the  inventory related problems we would be tackling by implementing the MRP module: reducing  planning time and being able to execute it more often, and reducing the probability of incurring  in a stock-out or an over stock. This would be the best way to get our manager approval.

Application

Using bar graphs and intuitive pictures (such as empty shelves or accumulated materials due to  imprecise purchasing), through a classic PowerPoint presentation, we presented our project to  the manager. We focused on the current situation (what is?) and the potential situation to which  we would arrive in the event of correctly executing the project (what if?).

Insight

Despite the presentation went well, we realized we haven’t fully considered the impact this  project would have in the Procurement Department (on which our department depended on),  as they workload would have suffered a considerable increase. This was, as I can see now,  because we weren’t empathetic enough and didn’t consider an important stakeholder the way  we were supposed to. In any case, it was a valuable insight as it helped us significantly in future  projects.

Approach

The weeks following our presentation, we focused on preparing a learning launch of the module,  by only using it in a few selected materials, to have a better understanding of the effects it would  have on the whole planning/purchasing process.  Looking back, I think it wasn’t a bad idea, but  we probably should’ve focused even more in the needs of the Procurement Department, as now  I understand it would have saved us a lot of time. As Design Thinking has taught me, the focus  on the user and the stakeholders must be maintained as a main guide during the entire project  management process.


Example Reflection – Visualization Challenge I was working as an Inventory Analyst in the Logistics Department of a natural gas distribution company , and together with my boss , we were designing a project that intended to replace our current inventory management system ( which was based on the use of spreadsheets ) for the MRP ( Materials Requirement Planning ) module that was included in our SAP ERP system , but has never been used before . After doing some analysis , we concluded that it would allow us to enhance our materials requirement planification time and precision . However , we had to convince our manager about that . Selection In order to efficiently communicate our idea , I selected the Visualization tool ( though in that time I was not aware of it as a Design Thinking tool ) to convey a clear understanding of the inventory related problems we would be tackling by implementing the MRP module : reducing planning time and being able to execute it more often , and reducing the probability of incurring in a stock - out or an over stock . This would be the best way to get our manager approval . Application Using bar graphs and intuitive pictures ( such as empty shelves or accumulated materials due to imprecise purchasing ) , through a classic PowerPoint presentation , we presented our project to the manager . We focused on the current situation ( what is ? ) and the potential situation to which we would arrive in the event of correctly executing the project ( what if ? ) . Insight Despite the presentation went well , we realized we have n’t fully considered the impact this project would have in the Procurement Department ( on which our department depended on ) , as they workload would have suffered a considerable increase . This was , as I can see now , because we were n’t empathetic enough and did n’t consider an important stakeholder the way we were supposed to . In any case , it was a valuable insight as it helped us significantly in future projects . Approach The weeks following our presentation , we focused on preparing a learning launch of the module , by only using it in a few selected materials , to have a better understanding of the effects it would have on the whole planning / purchasing process . Looking back , I think it was n’t a bad idea , but we probably should ’ve focused even more in the needs of the Procurement Department , as now I understand it would have saved us a lot of time . As Design Thinking has taught me , the focus on the user and the stakeholders must be maintained as a main guide during the entire project management process .