1. Challenge:

I work in the telecommunications industry in the area of systems and business process design.

This time we have to design the external and internal infrastructure provisioning process.

For this, several areas participate, among the most representative are budgets, engineering,  purchasing and logistics, and obviously the area of systems and processes.

The challenge is to have budget control and ensure that this does not impact the supply chain, that  is, to coordinate budget events with purchasing and logistics processes.

2. Selection:

I have selected the mind mapping tool, since it will allow me to clarify the need of the areas  involved and to be able to map the way in which both the activities and the requirements are  taking shape and if necessary, this tool offers the possibility of moving each element, idea or  requirement in the same map to be able to shape it.

I take this idea from the video of week 2 (Mind mapping tool)

3. Application:

The first thing I did was to clarify the objective that needed to be reached, in this case it is that  senior management wants to:

• Control the budget

• Do not impact the purchasing and logistics processes

I asked each area of the business to do an analysis of the current activities that they carry out on a  day-to-day basis and that should be integrated into the new process. Additionally, they must list  restrictions and requirements that must be met in each of them.

Coordinate a work session so that each area presented the information prepared to the rest of the  team, in this way, each area would have knowledge of the steps that are executed by the rest of  the teams and already having a general context of all the elements, We were ordering them taking  into account:

• Prerequisites

• Dependencies

• Interleaved steps to be taken between areas

• Identification of possible impacts

• Essential activities

We did the first exercise and at the end we reviewed it together, going through the entire flow of  activities step by step and we realized that adjustments had to be made to what we had originally  defined.

Once the adjustments have been made and in consensus with the different areas, we define the  final version that would be presented to senior management.

This proposal was presented to the management and although there were comments and minimal  adjustments, the presented proposal complied with the requirements in 90%, therefore I consider  that the exercise was of great value.

4. Perspective:

When working on the definition of workflows, one of the main mistakes made is that we collect  the information, analyze it and present the proposals made by ourselves, without considering the  opinion, points of view and experience of the main involved in the execution of tasks or activities.

By working with a mind map, I understood how to involve the main stakeholders of the process, I  could have a greater and clearer idea of the needs and activities of each of them and by making  them aware of the activities in which the rest of the activities are involved. areas broadens the  knowledge of flow in general and it is much easier to map the step-by-step of a complex process.

5. Focus:

Next time, I would like to add STORY NARRATION to practice, since I consider that users can  present the narration of the activities they develop on a day-to-day basis, with these narrations,  we should take the most relevant comments so that in the end Let's use the mind map tool.

