<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Thiago Marquini Machado on Medium]]></title>
        <description><![CDATA[Stories by Thiago Marquini Machado on Medium]]></description>
        <link>https://medium.com/@thiago-marquini-machado?source=rss-3d975c9d5369------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eq61Mzinpfodja-XUEI0Vw.jpeg</url>
            <title>Stories by Thiago Marquini Machado on Medium</title>
            <link>https://medium.com/@thiago-marquini-machado?source=rss-3d975c9d5369------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 06:01:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thiago-marquini-machado/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Customer Epic #12 — Review]]></title>
            <link>https://thiago-marquini-machado.medium.com/the-customer-epic-12-review-185e04bbef75?source=rss-3d975c9d5369------2</link>
            <guid isPermaLink="false">https://medium.com/p/185e04bbef75</guid>
            <dc:creator><![CDATA[Thiago Marquini Machado]]></dc:creator>
            <pubDate>Sun, 20 Dec 2020 20:05:56 GMT</pubDate>
            <atom:updated>2020-12-21T00:04:57.810Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Customer Epic #12 — Review</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItM9-YZIPLhFLkCj-xnCjQ.jpeg" /></figure><p>This is the last post of this serie. It all started with the CXL Institute Growth Marketing course need for 12 posts. I seized the opportunity to better understand the whole customer journey within a company.</p><p>I realized that the various departments in the company are organized in silos and there is really not a unified concern about the customer throughout them. The project or product team does not even take the customer into account.</p><p>Let´s make the retrospective of our findings:</p><p>#1. We understood that customer journey must be unified within the Commercial Funnel. Marketing, prospecting, sales and customer service must be a single funnel. Then, we have to understand the customer journey within the project in order to reach a integrated customer journey: the customer epic!</p><p>#2. We built the Commercial Funnel. We stopped at customer service because there is the interconnection with the project and we have to better understand the project view of the customer.</p><p>#3. We found that the project view of the customer is… NONE. Project management simply does not address it. Treats the customer as any minor stakeholder. He is not! He is just the MAIN stakeholder. Embrace it.</p><p>#4. We had an overview on portfolio management and found that the customer is one of the key dimensions of strategic planning. There is no sustainable benefit and value attainment for the company if there isn´t any benefit or value to the customer.<strong> </strong>Ensuring that the customer is taken into account in strategic planning will make us think of him in every decision.</p><p>#5. We found that the customer really needs us to mentor him during his journey.</p><p>I have to confess I did not get all the answers I wanted. Although it became much more clear, I could not connect the loose ends yet, so I will just have to keep studying and being alert about these issues at work.</p><p>I will start to research about customer service and I hope I can understand the whole Customer Epic with that.</p><p>***</p><p><strong>About the CXL Institute Growth Marketing Minidegree</strong></p><p>Now that is almost over, I am looking back to the beginning of the course, 3 months ago, and wish to let my testimonial.</p><p>The course is quite demanding, since it have about 120 hours of video content, which is 40 hours per month. Besides, there is all the review posts you got to do in order to keep it free, each of the 12 with 1000 words.</p><p>Despite having all this hard work, the course is very good and worthy. All of the content is relevant. Of course you just cannot learn everything, so you will have to chose, among the 33 courses which one of them you are really going to dedicate yourself.</p><p>I feel much more prepared now. I really recommend this course to anyone who is looking for learning about modern marketing.</p><p>***</p><p>So here ends this journey about the customer epic. This is really just the beginning, there is much more to learn.</p><h3>Versão em Português</h3><p>Este é o último post desta série. Tudo começou com a necessidade do curso de Marketing de crescimento do CXL Institute para 12 posts. Aproveitei a oportunidade para entender melhor toda a jornada do cliente dentro de uma empresa.</p><p>Percebi que os vários departamentos da empresa estão organizados em silos e não há realmente uma preocupação unificada com o cliente em todos eles. A equipe de projeto ou produto nem leva em consideração o cliente.</p><p>Vamos fazer uma retrospectiva de nossas descobertas:</p><p># 1. Entendemos que a jornada do cliente deve ser unificada dentro do funil comercial. Marketing, prospecção, vendas e atendimento ao cliente devem ser um único funil. Então, temos que entender a jornada do cliente dentro do projeto para chegar a uma jornada do cliente integrada: a epopeia do cliente!</p><p># 2. Construímos o Funil Comercial. Paramos no atendimento porque existe a interligação com o projeto e temos que entender melhor a visão do projeto do cliente.</p><p># 3. Descobrimos que a visão do projeto do cliente é … NENHUMA. O gerenciamento de projetos simplesmente não trata disso. Trata o cliente como qualquer parte interessada secundária. Ele não está! Ele é apenas o principal interessado. Abrace isso.</p><p># 4. Fizemos uma visão geral da gestão de portfólio e descobrimos que o cliente é uma das dimensões-chave do planejamento estratégico. Não há benefício sustentável e obtenção de valor para a empresa se não houver benefício ou valor para o cliente. Garantir que o cliente seja levado em consideração no planejamento estratégico nos fará pensar nele em todas as decisões.</p><p># 5. Descobrimos que o cliente realmente precisa de nós para orientá-lo durante sua jornada.</p><p>Devo confessar que não obtive todas as respostas que queria. Embora tenha ficado muito mais claro, eu não consegui conectar as pontas soltas ainda, então terei apenas que continuar estudando e estar alerta sobre essas questões no trabalho.</p><p>Vou começar a pesquisar sobre atendimento ao cliente e espero poder entender toda a Epopéia do Cliente com isso.</p><p>***<br><strong>Sobre a Minigraduação em Growth Marketing do CXL Institute</strong></p><p>Agora que está quase acabando, estou olhando para o início do curso, há 3 meses, e gostaria de deixar meu depoimento.</p><p>O curso é bastante exigente, pois conta com cerca de 120 horas de conteúdo em vídeo, ou seja, 40 horas por mês. Além disso, há todos os posts de revisão que você precisa fazer para mantê-lo gratuito, cada um dos 12 com 1000 palavras.</p><p>Apesar de ter todo esse trabalho duro, o curso é muito bom e vale a pena. Todo o conteúdo é relevante. Claro que você não pode aprender tudo, então você terá que escolher, entre os 33 cursos, qual deles você realmente vai se dedicar.</p><p>Me sinto muito mais preparado agora. Eu realmente recomendo este curso para quem está procurando aprender sobre marketing moderno.</p><p>***</p><p>Então aqui termina esta jornada sobre o épico do cliente. Este é realmente apenas o começo, há muito mais para aprender.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=185e04bbef75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Customer Epic #11 — Review]]></title>
            <link>https://thiago-marquini-machado.medium.com/the-customer-epic-11-review-41e196ef25fa?source=rss-3d975c9d5369------2</link>
            <guid isPermaLink="false">https://medium.com/p/41e196ef25fa</guid>
            <dc:creator><![CDATA[Thiago Marquini Machado]]></dc:creator>
            <pubDate>Mon, 14 Dec 2020 20:19:54 GMT</pubDate>
            <atom:updated>2020-12-20T19:49:33.900Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Customer Epic #11 — Review</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItM9-YZIPLhFLkCj-xnCjQ.jpeg" /></figure><p>CXL Institute´s Growth Marketing course is about general marketing strategy. I still did not find anything that could really help us merge marketing, sales and the operation or project that will deliver the product. There is still this annoying gap.</p><p>Having watched the majority of the classes, I really do not think I will find this answer here. But it still really worth it. I am loving all the content.</p><p>***</p><p>Continuing our talk about project management and the client role:</p><p><strong>What are project management process groups?</strong><br>A Project Management Process Group is a logical grouping of project management processes to achieve specific project objectives. The Process Groups are independent of the project phases.</p><p>A project phase is a set of logically related activities that culminates in the completion of one or more deliverables.</p><p>For example, in a typical engineering project we have the conceptual design, executive design, supplies and construction phase. Each of these phases has its own characteristics and generates specific deliveries.</p><p>A Process Group, as recommended in PMBOK, will have its processes executed in the project as a whole, but they can also be executed completely in each phase.</p><p>The 5 Project Management Process Groups are:</p><p>Initiation Process Group<br>These are the processes carried out to define a new project or a new phase of an existing project, by obtaining authorization to start the project or phase.</p><p>The processes included in this group are:</p><p>Develop the project’s Charter;<br>Identify stakeholders.<br>Planning Process Group<br>They are the processes carried out to plan the project or the phase of a project, so that the execution and the monitoring and control are carried out in accordance with the Project Management Plan.</p><p>The processes included in this group are:</p><p>Develop the Project Management Plan;<br>Plan scope management;<br>Collect the requirements;<br>Define the scope;<br>Create the Project Analytical Structure (WBS);<br>Plan schedule management;<br>Define activities;<br>Sequencing activities;<br>Estimate the duration of activities;<br>Develop the schedule;<br>Plan cost management;<br>Estimate costs;<br>Determine the budget;<br>Plan quality management;<br>Plan resource management;<br>Estimate the resources of the activities;<br>Plan communications management;<br>Plan risk management;<br>Identify risks;<br>Perform qualitative risk analysis;<br>Perform quantitative risk analysis;<br>Plan risk responses;<br>Plan the management of acquisitions;<br>Plan stakeholder engagement.<br>Execution process group<br>These are the processes carried out to complete the work defined in the project management plan to satisfy the requirements of the project.</p><p>The processes included in this group are:</p><p>Guide and manage the work of the project;<br>Manage project knowledge;<br>Manage quality;<br>Acquire resources;<br>Develop the team;<br>Manage the team;<br>Manage communications;<br>Implement risk responses;<br>Conduct acquisitions;<br>Manage stakeholder engagement.<br>Monitoring and control process group<br>These are the processes required to monitor, analyze and control the progress and performance of the project, identify any areas in which changes to the plan will be necessary, and initiate the corresponding changes.</p><p>The processes included in this group are:</p><p>Monitor and control the work of the project;<br>Perform integrated change control;<br>Validate the scope;<br>Control the scope;<br>Control the schedule;<br>Control costs;<br>Control quality;<br>Control resources;<br>Monitor communications;<br>Monitor risks;<br>Control acquisitions;<br>Monitor stakeholder engagement.<br>Closing Process Group<br>And finally, we have the processes carried out to conclude or formally close a project, phase or contract.</p><p>The process included in this group is just the “End project or phase”.</p><p><strong>Conclusion of project management process groups</strong><br>Although the sequence presented is the usual one in most projects, the processes will not necessarily be carried out in this way, and may have the order changed, be suppressed, be carried out in an iterative way or at the same time as other processes.</p><p>The ideal way to approach each project should be defined by the Project Manager.</p><p><strong>What are PMBOK’s areas of expertise?</strong><br>A Knowledge Area, according to the PMBOK definition, is an area defined by your knowledge requirements and necessary in terms of the processes that comprise it: practices, inputs, tools and techniques.</p><p>They are interrelated, the Knowledge Areas are defined from the point of view of project management. They are used in most projects and most of the time.</p><p>What are the areas of knowledge of PMBOK?<br>The 10 areas of knowledge of PMBOK are:</p><p><strong>Integration management</strong>: processes and as activities to identify, define, combine, unify and coordinate the various project management processes and activities.<br><strong>Scope management</strong>: processes necessary to ensure that the project includes all the necessary work, and only the necessary, so that it ends successfully.<br><strong>Schedule management</strong>: localized processes to manage the timely completion of the project.<br><strong>Cost management</strong>: processes involved in planning, criteria, budgets, financing, cost management and control, so that the project can be eliminated within the approved budget.<br><strong>Quality management</strong>: processes for incorporating the organization’s quality policy in relation to the planning, management and control of project and product quality requirements to meet the expectations of related parties.<br><strong>Resource management</strong>: processes for identifying, acquiring and managing general physical or human resources for a well-defined project completion.<br><strong>Communications management</strong>: processes necessary to clear that project information is planned, collected, topped, distributed, stored, retrieved, managed, controlled, monitored and finally organized in a timely and appropriate manner.<br><strong>Risk management</strong>: processes for conducting risk management planning, identification and analysis, response planning, response implementation and risk monitoring in a project.<br><strong>Procurement management</strong>: internal processes to buy or acquire products, services or results external to the project team.</p><p>Management of parties, according to or interested parties: processes required to identify how people, groups or associations that may impact or be impacted by the project, analyze the expectations of the parties and their impact on the project, and develop the appropriate management for their effective engagement decisions and project execution.</p><p>The needs of a specific project may require one or more areas of additional knowledge, for example, a building may require financial management or health and safety management.</p><p>However, these 10 Knowledge Areas defined in the PMBOK are like that that must be addressed in each and every project.</p><p>The degree of planning and management effort used in each area depends on the complexity of the project, but the Project Manager must be attentive to each of them, albeit informally.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41e196ef25fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Customer Epic #10 — Review]]></title>
            <link>https://thiago-marquini-machado.medium.com/the-customer-epic-10-review-d76740d4188e?source=rss-3d975c9d5369------2</link>
            <guid isPermaLink="false">https://medium.com/p/d76740d4188e</guid>
            <dc:creator><![CDATA[Thiago Marquini Machado]]></dc:creator>
            <pubDate>Fri, 04 Dec 2020 12:32:13 GMT</pubDate>
            <atom:updated>2020-12-15T10:48:04.900Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Customer Epic #10 — Review</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItM9-YZIPLhFLkCj-xnCjQ.jpeg" /></figure><p>CLX Growth Markwting course is now on Facebook Ads.</p><p>***</p><p>Continuing our talk about project management and the client role:</p><p>All experienced project managers use well-established project management methodologies such as PMBOK, FEL or PRINCE2, but they can also be organization-specific internal methodologies.</p><p>These approaches have different emphases and tend to use slightly different terminology, but they generally share two main characteristics: projects are delivered in stages and certain common project management processes are performed in these stages.</p><p><strong>What is the life cycle of a project?</strong><br>The project life cycle is the series of phases that a project goes through, from start to finish.</p><p>It provides the basic framework for project management. This basic structure applies regardless of the work of the specific project involved. The phases can be sequential, iterative or overlapping.</p><p>Project life cycles can be:</p><p>Predictive: you know exactly what to do and plan it step by step from the beginning of the project;<br>Adaptive: you plan each phase according to the increased knowledge of the project during its execution.<br>The approach can also be hybrid, predictive in some phases and adaptive in others.</p><p>Predictive life cycles are also called cascading life cycles. While adaptive life cycles are also called agile or change-oriented life cycles.</p><p>It is up to the project management team to determine the best life cycle for each project. The project life cycle needs to be flexible enough to handle the variety of factors included in the project. Life cycle flexibility can be achieved through:</p><p>Identification of the process or processes that need to be performed at each stage;<br>Execution of the process or processes identified at the appropriate stage;<br>Adjusting the various attributes of a phase.</p><p><strong>What are the stages of a project?</strong><br>The stages of a project are a set of activities related in a logical manner that culminates in the completion of one or more deliveries.</p><p>Phases or steps are very important for project managers. Thinking in terms of phases, you can ensure that deliveries produced at the end of each phase meet your purpose, and that project team members are adequately prepared for the next phase.</p><p>You identify the deliverables required for each phase in the Project Analytical Structure (WBS) or, in English, Work Breakdown Structure (WBS). The WBS is designed as part of your preparation activities and then validated by the rest of the project team.</p><p>Once deliveries are approved, and only after they are approved, the phase is completed and the project team can go through the “gate” to the next phase. That is why the term is often used in project management.</p><p>In your preparation phase, think about who needs to approve each delivery. Approvers can include the project board, the project sponsor or the client.</p><p>The phases and the order in which they are completed can vary, depending on what you need to achieve and the nature of the project, but as a rule include:</p><p><strong>Business case or feasibility study</strong><br>In this phase, you define the benefits generated by the project according to a perceived need.</p><p>The gate at the end of this phase is the approval of your project proposal. You must also show that you can achieve the project’s goals within the required deadlines and budget.</p><p><strong>Preparation or initiation</strong><br>At this stage the project begins. You work with project stakeholders and team members who have already been identified to establish and initiate the project.</p><p>Here, the objectives, benefits, restrictions, assumptions and risks of the project are defined more precisely than in the business case. It’s the kickoff.</p><p><strong>Planning</strong><br>Here you determine how you will work to achieve the objectives proposed by the project.</p><p>To do this, work with team members and strategic stakeholders to produce detailed plans for each subsequent phase. Determine the WBS, budget, schedule and resources needed and how to acquire them.</p><p>What’s more, go deeper into identifying risks, classifying them and creating contingency plans. Determine how communications will be made, how quality will be addressed and how stakeholders will be engaged.</p><p><strong>Development, design or project</strong><br>At this stage, you begin the work involved in creating the project deliverables. Then, work with relevant stakeholders to develop the designs for the main products.</p><p>At this stage, you must do everything you can to think and deal with the project’s problems before you start creating the project deliverables. Remember, problems are always easier and cheaper to fix at the design stage than at deployment.</p><p><strong>Development and testing or construction and commissioning</strong><br>With all the planning and design complete, the project team can now begin to develop and build the components of the outputof the project — be it software, a bridge or a business process.</p><p>As part of this phase, you need to test these components thoroughly to confirm that they work as they should.</p><p><strong>Start-up, transition and training</strong><br>This step is all about preparing for the project launch or start-up.</p><p>Train users or operators, put in place continuous support and identify what is necessary for the project to be effective from the launch or delivery date.</p><p><strong>Support and benefit realization</strong><br>Be sure to provide transition support after the project is delivered. Project teams are often assigned to other jobs very early after the project has been transferred, which means that the benefits of the project are often not fully realized.</p><p><strong>Monitor the delivery of project benefits.</strong></p><p>You can use this to promote your project or provide information about other actions needed to ensure that your project is successful. You can and should continue to do so after the project is closed.</p><p><strong>Closing </strong><br>Closing a project is not the most interesting part of the project’s life cycle, but if you don’t do it properly it can obstruct the continued delivery of benefits to the organization.</p><p>Fill out and store the documentation. Conduct a post-deployment review, so that you and your colleagues can use the experience you have gained in future projects, you do not want to lose the experience and knowledge they gained from working on the project.</p><p><strong>Conclusion on life cycle and stages of a project</strong><br>It is up to the Project Manager to determine the project life cycle approach, as well as to define the project phases and the processes to be used in each phase.</p><p>So there is no cake recipe that can be used in any and all projects, and there should always be a customization.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d76740d4188e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Customer Epic #9 — Review]]></title>
            <link>https://thiago-marquini-machado.medium.com/the-customer-epic-9-review-4f0503afd1d3?source=rss-3d975c9d5369------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f0503afd1d3</guid>
            <dc:creator><![CDATA[Thiago Marquini Machado]]></dc:creator>
            <pubDate>Sun, 29 Nov 2020 20:18:22 GMT</pubDate>
            <atom:updated>2020-12-20T19:45:47.111Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Customer Epic #9 — Review</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItM9-YZIPLhFLkCj-xnCjQ.jpeg" /></figure><p>CLX Growth Marketing course is now about Data-driven influencer marketing, by Siim Säinas. Very good content.</p><p>The courses on Public Relations and Google Ads are quite interesting too.</p><p>Anyway, this whole course has lots of information about several diferent growth areas and aspects. Of course you cannot really learn all this content because 3 months are short time for 112 hours, but for sure all you can learn is worthy,</p><p>***</p><p>Continuing our series about project management and the client role.</p><p><strong>What is it and what are the types of organizational structure in projects?</strong></p><p><strong>What is matrix structure, functional and project oriented?</strong><br>You may have come across the term “matrix structure” by reading an article on business organization, or text on project management or even a job description.</p><p>But what does matrix, functional or project-oriented structure mean?</p><p><strong>What is organizational structure?</strong><br>The organizational structure is the way the company is organized around the division of activities and resources.</p><p>It is the formal system of authority relationships, tasks and processes and determines how people coordinate their actions and use resources to achieve organizational goals.</p><p>For example, a small business usually has the following structure as shown in the chart below:</p><p><strong>Organizational structure</strong></p><p>In this structure, the owner determines what should be done, passes the instructions to the employees who perform the tasks and returns the delivery to the owner. It is a very simple hierarchy and the process flow has only one direction, owner to employee.</p><p>For a company to function, it is necessary to comply with accounting and legal obligations, manage finances, recruit or fire employees, among a range of functions that do not directly concern what the company produces or the service it provides.</p><p>If the company’s operation is small, this owner can assume all these functions, outsource them or assign them to one or more employees. That’s when it starts to complicate.</p><p>Now imagine a multinational with 10,000 employees, operating in more than 40 countries with billions of dollars in annual revenue. A much more complex structure is obviously needed!</p><p>We will then have an extremely hierarchical structure, ranging from the CEO, through the boards, managements, coordinations, to the operational staff.</p><p>We will also have many departments to deal with each of the areas that the owner of our small business dealt with alone.</p><p>There will be the HR, marketing, engineering, IT, production, research and development, finance, accounting department, in short, as many departments as necessary.</p><p>These departments can be replicated in each business unit of the company, each office or factory.</p><p>Within this hierarchy and departmentalization we have a gigantic flow of processes and information, so that tasks are accomplished and properly informed.</p><p>The organization chart of this company would be extremely complex and to visualize it it would be necessary to separate it into several parts.</p><p>Factors that determine the organizational structure<br>There are countless factors that the organization considers for inclusion in its organizational structure. Each factor can have a different level of importance in the final analysis.</p><p>Include, but are limited to:</p><p>Degree of alignment with the organization’s objectives;<br>Specialization capabilities;<br>Extent of control, efficiency and effectiveness,<br>Clear line and scope of authority;<br>Delegation capabilities;<br>Assignment of accountability;<br>Assignment of responsibilities;<br>Cost considerations;<br>Physical locations (for example, co-located, regional and virtual); and<br>Clear communications (for example, policies, job status and vision of the organization).<br>Types of organizational structure<br>We basically have 3 types of organizational structure:</p><p><strong>Functional structure</strong><br>It is the type of structure most used in companies. You probably work or have worked in a functional organization.</p><p>There, similar operations are grouped into departments. It is hierarchical in nature. Employees are subordinate to a manager, who in turn is subordinate to a higher-level manager, and so on.</p><p>Departments are organized around similar processes and employees have similar skills, ranging from assistants to specialists.</p><p>The advantages of this structure are:</p><p>Clear chain of command;<br>Cohesive and specialized team;<br>Clear separation of functions.<br>The disadvantages are:</p><p>High bureaucracy and rigidity of processes;<br>Project manager usually divides time with a department function;<br>Limited authority of the Project Manager, as it conflicts with the department manager.</p><p><strong>Structure by projects</strong><br>Project organizations focus on the projects themselves, not the department’s work.</p><p>Project managers have maximum authority over resources and other functions such as accounting, supplies and HR may be subordinate to the project manager, as they are support functions.</p><p>The advantages of this structure are:</p><p>Lean hierarchy;<br>The project manager makes the decisions and has maximum authority;<br>The organization’s objective is to work on the project.<br>The disadvantages are:</p><p>Idle time in phases between projects;<br>Competition for the best resources;<br>Uncertainty of permanence in the framework at the end of a project.<br>Matrix structure<br>Matrix organizations combine the functional structure with that of projects. The organization’s structure is hierarchical and functional,with their departments and managers.</p><p>However, when it comes to projects, the Project Manager designates a team that can be composed of exclusive project members and members who have a functional role in a department.</p><p>This second type of member must answer to the Project Manager, if he is working on the project or to the department manager, if he is carrying out the functional work. He divides his time between tasks.</p><p>Strong matrix organizations emphasize projects, that is, the Project Manager will have greater authority over the functional manager. The opposite is true in weak matrix organizations.</p><p>The advantages of this structure are:</p><p>The organization’s focus is on project work;<br>There may be specialized resources that benefit the project;<br>Project work will bring a greater opportunity for evolution than just department work.<br>The disadvantages are:</p><p>Employees can have more than one boss, whether they work on the job or on the project;<br>There may be confusion of roles and responsibilities;<br>There may be conflict between managers.</p><p><strong>Conclusion on organizational structure</strong><br>The Project Manager must identify what type of structure he is working on, as this will change his approach.</p><p>He may have more or less authority and resources depending on the company’s organizational structure and must deal with it accordingly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f0503afd1d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Customer Epic #8 — Review]]></title>
            <link>https://thiago-marquini-machado.medium.com/the-customer-epic-8-review-910e3a3d701f?source=rss-3d975c9d5369------2</link>
            <guid isPermaLink="false">https://medium.com/p/910e3a3d701f</guid>
            <dc:creator><![CDATA[Thiago Marquini Machado]]></dc:creator>
            <pubDate>Sun, 22 Nov 2020 07:17:07 GMT</pubDate>
            <atom:updated>2020-12-15T10:31:04.371Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Customer Epic #8 — Review</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItM9-YZIPLhFLkCj-xnCjQ.jpeg" /></figure><p>The most interesting class I had this week on CLX Institute´s Growth Marketing course was “Optimizing your marketing stack”, by Dan McGaw. He teaches how to choose and integrate the tools in your martech stack.</p><p>***</p><p>We´ve been talking about how we must aim the client in project management, but what is project management?</p><p>Nowadays much is said in the corporate environment or even in public institutions about the management or management of projects.</p><p>But what exactly does it mean by term?</p><p>To help you understand the modern meaning of project management, let’s first define what a project is.</p><p><strong>What is a project?</strong><br>There are thousands of project definitions, for me the most complete is that of PMBOK that says:</p><p>A project is a temporary effort undertaken to create a unique product, service or result.</p><p>Given the definition, we must understand a unique product, service or result as:</p><p>A new component or item;<br>An enhancement of an item;<br>A correction of an item;<br>Generation of the ability to perform a service;<br>A document;<br>A study;</p><p>Or a unique combination of one or more products, services or results.<br>That is, a project can create several different things. Therefore, the important thing in the definition is the term “unique”, which means that a project will deliver something that is specific, special and exclusive.</p><p>The temporary effort, or a temporary endeavor, means that the project has a defined start and end.</p><p>This does not mean that a project has a short duration, as there are projects that last for years or decades.</p><p>This phrase simply means that a project has a determined beginning and end, which can occur for several reasons, such as the completion of the delivery for which the project was started or its cancellation.</p><p><strong>Why carry out a project?</strong><br>The key to understanding why organizations or people do projects is that they drive change!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JkrLtHPTDEDJPJrV.jpg" /></figure><p>For example, if you intend to develop your project management skills through a postgraduate degree in the field, it means that you are going to start a project.</p><p>In other words, graduate school is a temporary effort of one or two years, which will generate a unique result, your specialization in project management.</p><p>The delivery of this unique result is proven through the diploma, which is the document that proves this training in project management.</p><p>Well, this way we have that the postgraduate is a project.</p><p>Another example, if a company decides to set up an industrial park in a new location, for economic and logistical reasons, it will start a project.</p><p>In this case, the project period will extend from the factory design to the delivery of the construction and start of operation. The only result is the new factory itself, a new business unit.</p><p>In other words, a project is an enterprise used to move from the current state to the desired state, as shown in the figure below:</p><p><strong>Project organization</strong></p><p>There are many reasons that can lead to the need for change, whether on a personal or organizational level.</p><p>And the safest way to materialize these transformations is through good project management.</p><p>That is why projects are considered strategic and fundamental for companies and for their personal and professional life.</p><p>But after all, what is project management?<br>Project management is the application of knowledge, skills, tools and techniques to project activities in order to meet their requirements.</p><p>Project management is performed through the application and integration of the management processes identified for the project.</p><p><strong>Benefits of project management</strong><br>Project management allows organizations and people to carry out projects effectively and efficiently.</p><p>Good project management helps individuals, groups and companies to:</p><p>Meet business objectives;<br>Satisfy the expectations of interested parties, or stakeholders;<br>Be more predictable;<br>Increase your chances of success;<br>Deliver the right products at the right time;<br>Solve problems and issues;<br>Respond to risks in a timely manner;<br>Optimize the use of organizational resources;<br>Identify, recover or eliminate projects with problems;<br>Manage constraints (for example, scope, quality, schedule, costs, resources);<br>Balance the influence of project constraints (for example, increasing scope may increase costs or lead time); and<br>Manage changes better.</p><p>On the other hand, running any project without using project management or managing projects poorly can result in:</p><p>Missed deadlines;<br>Budget overflows;<br>Bad quality;<br>Rework;<br>Uncontrolled expansion of the project;<br>Loss of reputation for the organization;<br>Dissatisfied stakeholders; and<br>Inability to achieve the objectives for which the project was undertaken.<br>What is the difference between operations and projects?<br>Most of the work done in organizations can be described as operational or project work.</p><p>However, it is very important to understand that there are fundamental differences between the two activities.</p><p>Therefore, the management approach of one or the other will not be the same, even though several tools and processes are used successfully in both.</p><p>The definition of operation can be very similar to the definition of project. For example, when searching for “operation” on Google, you will find:</p><p>“The set of acts or measures that combine the means to obtain certain results or certain objectives”.</p><p>Now, the confusion is evident! But what would be the difference then?</p><p>The first and main difference is that the project is temporary, the operation is continuous.</p><p>For example, a company may decide to put a product into production over a 20-year horizon. We have a defined time interval, but there is continuity in the work carried out in an operation.</p><p>In other words, production will follow exactly the same procedures over these 20 years, that is, production will always be carried out in this new way. So it is an operation.</p><p>On the other hand, the project follows a life cycle (a subject that we will address in other articles). It has the phases of technical and economic feasibility study, conception, design, construction or implantation and delivery, and may also have other phases.</p><p>Thus, if there is a need to change the operation or the product, a new project will be carried out.</p><p>Once the project is completed, the new procedures are transferred to the operation and the cycle begins again. This is the relationship between operation and project. Projects drive the necessary changes in operations.</p><p>Therefore, the methodology for managing an operation will not be suitable for project management, and vice versa.</p><p>Because in the project there is a certain degree of uncertainty (which can be very high), and it is necessary to manage the risks, requirements and expectations of each stakeholder.</p><p>In addition to the need to manage the knowledge acquired during the project (which in the case of an operation is already intrinsically added to it, while in the project it can be lost), among other factors to be addressed.</p><p><strong>Conclusion on what is project management</strong></p><p>Efficient project management is essential for organizations to improve their operations safely and economically.</p><p>On the other hand, the speed of changes in the organization due to new technologies is constantly increasing.</p><p>Thus, we conclude that knowing the project management methodology is increasingly important for professionals in all areas.</p><p>Por outro lado, a velocidade das mudanças na organização devida as novas tecnologias não para de aumentar.</p><p>Desta forma, concluímos que conhecer a metodologia de gerenciamento de projetos é cada vez mais importante para os profissionais de todo as áreas.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=910e3a3d701f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Customer Epic #7 — Review]]></title>
            <link>https://thiago-marquini-machado.medium.com/the-customer-epic-7-review-b702e4c59e11?source=rss-3d975c9d5369------2</link>
            <guid isPermaLink="false">https://medium.com/p/b702e4c59e11</guid>
            <dc:creator><![CDATA[Thiago Marquini Machado]]></dc:creator>
            <pubDate>Sun, 15 Nov 2020 10:06:29 GMT</pubDate>
            <atom:updated>2020-12-22T00:13:30.418Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Customer Epic #7 — Review</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItM9-YZIPLhFLkCj-xnCjQ.jpeg" /></figure><p>In the Growth Marketing course at the CXL Institute I had a very interesting class on Account Based Marketing. The teacher, Steve Watt, in addition to presenting a excellent content throughout the course, begins with a fantastic story.</p><p>He says that as soon as he joined a company when he was starting in Account Based Marketing to lead the team, he realized that everyone was very good and that they did everything with excellence, leaving little that he could do to stand out. That was when he realized that he would have to do something far beyond.</p><p>He realized that there were a number of strategic customers that were not in the company’s account and that they really should be. The leads were young people in the financial area who worked long hours a week and earned a lot of money. These people were looking for a meteoric rise and had little time available to meet salespeople.</p><p>His idea was to send a miniature Ferrari to all of them saying it was going to help them get there faster. From that he managed to reach almost a thousand accounts.</p><p>He understood how to create rapport with these ambitious and unavailable professionals: talking about them.</p><p>This is valid for each and every customer. We are used to focusing on ourselves. How our product is very good, how many outstanding features it has and how reliable our company is. This is important, but the customer will be able to see it for themselves. You don’t need a marketer or salesman doing this.</p><p>The customer wants to know what is in it for him. When we change the key from being self-centered or product-centered to customer-centered, the game gets good.</p><p>Try to date a girl by talking about yourself all the time and try to win her by talking about her and you will see the difference.</p><p>For me, among our the courses available in the Growth Marketing Minidegree that was the most insightful, until now.</p><p>***</p><p>About the Epic of the Customer:</p><p>I got really frustrated about the lack of addressing of the customer in the base of knowledge of the Project Management.</p><p>I will dive deeper into it to try to dig something out of it.</p><p>Being a 10 years plus PMP certified project manager makes it kind of embarrassing. Until know only portfolio management adressed the customer, but it is a strategical management. It have to adress him.</p><p>No wonder that so many projects fail.</p><p>+++</p><h3>Para os lusófonos:</h3><p>No curso de Growth Marketing do CXL Institute tive uma aula muito interessante sobre Account Based Marketing. O professor, Steve Watt, além de apresentar um excelente conteúdo ao longo de todo o curso, começa com uma história fantástica.</p><p>Ele conta que logo que entrou para uma empresa quando estava iniciando em Account Based Marketing , para liderar o time, percebeu que todos eram muito bons e que faziam tudo com excelência, restanto pouco que ele pudesse fazer para se destacar. Foi quando percebeu que teria que fazer algo muito além.</p><p>Percebeu que havia uma série de clientes estratégicos que não estavam na conta da empresa e que deveriam estar de qualquer maneira. Os contatos eram jovens da área financeira que trabalhavam muitas horas por semana e ganhava muito dinheiro. Este pessoal buscava uma ascensão meteórica e tinha pouco tempo disponível para atender os vendedores.</p><p>Sua ideia foi enviar uma miniatura da Ferrari para todos eles dizendo que ia ajudá-los a chegar lá mais rápido. Conseguiu a partir disso alcançar quase mil contas.</p><p>Ele entendeu como criar rapport com estes profissionais ambiciosos e indisponíveis: falar sobre eles.</p><p>Isso é válido para todo e qualquer cliente. Estamos habituados a focar em nós mesmos. Como nosso produto é muito bom, quantas funcionalidades fora de série ele tem e como nossa empresa é confiável. Isso é importante, mas o cliente vai conseguir perceber isso sozinho. Não precisa de um marqueteiro ou um vendedor martelando isso.</p><p>O cliente quer saber o que você tem para ele. Quando mudamos a chave de ser autocentrado ou centrado no produto para centrado no cliente é que a brincadeira fica boa.</p><p>Tente conquistar uma mulher falando sobre você o tempo todo e tente conquistá-la falando sobre ela e verá a diferença.</p><p>Para mim, entre os nossos cursos disponíveis no Minidegree de Marketing de Crescimento foi o mais interessante até agora.</p><p>***</p><p>Sobre a Epopeia do Cliente:</p><p>Fiquei muito frustrado com a falta de endereçamento do cliente na base de conhecimento do Gerenciamento de Projetos.</p><p>Eu vou mergulhar mais fundo nele para tentar extrair algo dele.</p><p>Sendo um gerente de projeto certificado PMP há mais de 10 anos torna isso um tanto embaraçoso.</p><p>Até agora só a gestão de portfólio pontua o cliente, mas é uma gestão estratégica. Tem que pontuá-lo.</p><p>Não é à toa que tantos projetos falham.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b702e4c59e11" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Customer Epic #6 — Review]]></title>
            <link>https://thiago-marquini-machado.medium.com/the-customer-epic-6-review-39b1cea1af65?source=rss-3d975c9d5369------2</link>
            <guid isPermaLink="false">https://medium.com/p/39b1cea1af65</guid>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[portfolio-management]]></category>
            <category><![CDATA[customer-epic]]></category>
            <category><![CDATA[customer]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Thiago Marquini Machado]]></dc:creator>
            <pubDate>Sun, 08 Nov 2020 12:31:44 GMT</pubDate>
            <atom:updated>2020-12-22T00:15:17.485Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Customer Epic #6 — Review</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItM9-YZIPLhFLkCj-xnCjQ.jpeg" /></figure><p>Last week we realized that the customer needs us (the company) to mentor him during his journey.</p><p>We found too that as soon as we bought him in, we just disappear.</p><p>Like Dungeon Master left the kids or Gandalf left Bilbo and then Frodo (this is recurring revenue!) all by themselves.</p><p>The problem is that the customer <em>may </em>do it alone, but he´ll <em>certainly </em>do one thing right after that: curse us!</p><p>And this is NOT recurring revenue.</p><p>…</p><p>Talkin about the <strong>Customer Epic</strong>(!) we found that in the domain of project management, the <strong>portfolio management</strong> is the one which address the customer, hence he is, at least, a strategic issue. But not necessarily a concern.</p><p>That may happen because portfolio management, in its position and duty, should make this concern percolate into the operational level and the project management itself.</p><p>Without the front of the army fighting for the customer, the strategic issue is talk, talk, only talk.</p><p>…</p><p><strong>CXL </strong>got quite interesting this time. They have a course called “<a href="https://cxl.com/institute/online-course/retention/#:~:text=Retention%20is%20the%20most%20underrated,catch%20on%20a%20regular%20basis."><em>Retention: the most underrated growth channel</em></a>”. The girl who teaches it is just amazing, and very patient with our total lack of comprehension of the customer. Her name is <strong>Val Geisler</strong>.</p><p>Here´s the funnel she presented, which is not a funnel anymore, it´s a kind of weird whirlpool of client nurturing. With that I may be able to adjust and continue my customer funnel (which may be a pipeline or another whirlpool or even a fancy spiral, who knows?).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XSAUn13GM0im4q9UJo16Nw.png" /></figure><p>Customer centricity states that we have to do everything for the right customers, and little for the others. She says the same. We´re gonna spend money on the wrong customer if you don´t know who is your right customer.</p><p>Anyway, the wrong one is only wrong because WE are not able to solve his problem. At least not yet.</p><p>It´s good to finally find a reference.</p><p>+++</p><h3>Aos lusófonos:</h3><p>Na semana passada percebemos que o cliente precisa de nós (a empresa) para orientá-lo durante sua jornada.</p><p>Descobrimos também que assim que o fazemos comprar simplesmente desaparecemos.</p><p>Como o Mestre dos Magos deixou as crianças ou o Gandalf deixou Bilbo e depois Frodo (isto é receita recorrente!) por conta própria.</p><p>O problema é que o cliente pode fazer isso sozinho, mas com certeza fará uma coisa logo depois: nos amaldiçoar!</p><p>E isto NÃO é receita recorrente.</p><p>…</p><p>Falando sobre o Épico do Cliente descobrimos que no domínio da gestão de projetos é a gestão de portfólio que enxerga o cliente. Ele é, pelo menos, uma questão estratégica. Mas não necessariamente uma preocupação.</p><p>Isso pode ocorrer porque a gestão de portfólio, em seu posição e dever, tem que fazer com que esta preocupação percole no nível operacional e na própria gestão de projetos.</p><p>Sem o fronte lutando pelo cliente, a questão estratégica é só conversa.</p><p>…</p><p>O curso do CXL Institute ficou bem interessante dessa vez. Eles têm um curso denominado “Retenção: o canal de crescimento mais subestimado”. A garota que ensina é simplesmente incrível e muito paciente com nossa total falta de compreensão sobre o cliente. O nome dela é Val Geisler.</p><p>Aqui está o funil que ela apresentou (vide diagrama acima), que não é mais um funil, é uma espécie de vórtice de nutrição de cliente. Com isso creio que poderei ajustar e continuar meu funil do cliente (que pode ser um pipeline ou outro redemoinho ou até mesmo uma espiral arrojada, quem sabe?).</p><p>A centralidade no cliente afirma que temos que fazer tudo pelos clientes certos e pouco pelos demais. Ela diz o mesmo. Vamos gastar dinheiro com o cliente errado se soubermos quem é o seu cliente certo.</p><p>Enfim, o errado só está errado porque NÓS não conseguimos resolver o problema dele. Ainda não.</p><p>É bom finalmente encontrar uma referência.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39b1cea1af65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Customer Epic #5 — Review]]></title>
            <link>https://thiago-marquini-machado.medium.com/the-customer-epic-5-review-9be00aa4fe80?source=rss-3d975c9d5369------2</link>
            <guid isPermaLink="false">https://medium.com/p/9be00aa4fe80</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[customer]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[customer-success]]></category>
            <dc:creator><![CDATA[Thiago Marquini Machado]]></dc:creator>
            <pubDate>Sat, 31 Oct 2020 23:34:13 GMT</pubDate>
            <atom:updated>2020-11-04T11:18:34.323Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Customer Epic #5 — Review</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItM9-YZIPLhFLkCj-xnCjQ.jpeg" /></figure><p>Let´s make a little retrospective here:</p><p>#1. We understood that customer journey must be unified within the Commercial Funnel. Marketing, prospecting, sales and customer service must be a single funnel. Then, we have to understand the customer journey within the project in order to reach a integrated customer journey: the customer epic!</p><p>#2. We built the Commercial Funnel. We stopped at customer service because there is the interconnection with the project and we have to better understand the project view of the customer.</p><p>#3. We found that the project view of the customer is… NONE. Project management simply does not address it. Treats the customer as any minor stakeholder. He is not! He is just the MAIN stakeholder. Embrace it.</p><p>#4. We had an overview on portfolio management and found that the customer is one of the key dimensions of strategic planning. There is no sustainable benefit and value attainment for the company if there isn´t any benefit or value to the customer.<strong> </strong>Ensuring that the customer is taken into account in strategic planning will make us think of him in every decision.</p><p>…</p><p>Meanwhile CXL Institute´s Growth Marketing course is quite interesting. Among the other lessons, I really found the Landing Page Optimization and YouTube Ads lessons very insightful and nice to watch.</p><p>Yeah, I just dumped A/B Testing Mastery for a while. Goddammit, that guys is really annoying, yet he knows what he is talking about.</p><p>…</p><p>Got stuck. Creative blackout. Infinite laziness. In front of the giant amount of work I need to do and understand I rather take a beer.</p><p>…</p><p>Still have to write 500 words tonight. So, beer in hands, let´s restart.</p><p>Dissection of the issue: immediate available project management knowledge base do not address customer. Must research on academic field. Hate those pricks. Having graduated in a Brazilian public school exposed me to them in a very disadvantaged position. Do not do that if you can.</p><p>I really don´t know what customer service is about. I had a commercial establishment and that was the closer I got to it. The business broke so I guess it have something to do with that.</p><p>Good, we have a door.</p><p>…</p><p>This thing never reaches 500 words. Enter the door.</p><p>Who really was in touch with customer at that time was Fernando, a partner who to took care of the store attendance. He used to spend a lot of time just chatting with customers. The relationship I see is that of an authority. They really rely on him about what we were selling.</p><p>My wife was a partner too. Big trouble.</p><p>At that time she was taking care of company´s relationship with suppliers, government leeches and accounting people. Now she is working in a major Brazilian electronics and furniture retailer in… customer service.</p><p>I´ll have make friendship with her again.</p><p>…</p><p>To make that a 500 let´s just establish what we are going to do next.</p><ul><li>talk to wife;</li><li>think about our service back then, while reexperiencing the shitty experience it was;</li><li>come up with something.</li></ul><p>…</p><p>Well, I´ll talk to her latter.</p><p>Let´s get back to the time I owned a shop. All the customers wanted from us is that, being the authority on the subject, we would help them go trough their journey. It´s always that way.</p><p>The customer rely on the company believing we are able to show him the path, remove any doubt or barrier and deliver the result he wanted. As we know, he may even not know what exactly he want. He may need us to help him discover it.</p><p>So that is the objetive of any person having a relationship with any company: it is that of a <strong>mentoring</strong>!</p><p>In order to happen at first place there must be <strong>credibility</strong>. That´s why companies spend lots of money in branding. To build it up.</p><p>It may sound very obvious all that stuff, but we really get kind of submerged under the business processes streams and most of the times forget why we are doing something, just because it really works without we being aware of the big picture.</p><p>Assume you are just a intern in your first job. You will be taught a bunch of processes in order to fulfill your tasks. You may not have any idea what for, but you may get quite good at that. You manage to be hired and goes up in the department ladder, always improving, and still not knowing exactly why you are doing that. Some business bigshot established these processes and you are following what was established, just that.</p><p>People even retire (with good money) without realizing the whys.</p><p>In a organizational level it happens too. Everyone is so caught in routine tasks while the company is growing that they forget what it is all about.</p><p>It´s all about the customer. It always have been.</p><p>…</p><p>Back to the very center of the business we remember that our mission is to be credible enough for the customer choose us as their mentor through his buying journey.</p><p>But we are really talkin about the customer epic! It is not just any journey. It is the whole sh*t.</p><p>In an epic we have a hero — the customer — who must fulfill a great mission through many obstacles — buy something — and is helped by a mythological being — the company — to accomplish an extraordinary feat— buying right.</p><p>This mythological being can both help or spoil his journey.</p><p>I like these analogies because they help us to put everything together. Now we have the roles and the plot.</p><p>…</p><p>The big problem I´m trying to address since the beginning is that, in most cases, in a purchase that requires any level of customization and therefore demands a project to be done, while the company is executing the project the customer stays out of the play.</p><p>For him what is happening now is a black box. That is the point when issues starts to arise within the project and are “solved” without the customer´s perspective being taking into account.</p><p>Meanwhile he is pulling out his hair because he doesn´t know what is happening with the most important thing: his money!</p><p>Is the company doing the right thing? Is it really what I´ve purchased? Why do they don´t talk to me?</p><p><strong>The customer have committed his money and do not have the right of even being communicated about what is going on?</strong></p><p><strong>According to the general level of business maturity, NO</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9be00aa4fe80" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Customer Epic #4 — Review]]></title>
            <link>https://thiago-marquini-machado.medium.com/the-customer-epic-4-review-b08ffcef7731?source=rss-3d975c9d5369------2</link>
            <guid isPermaLink="false">https://medium.com/p/b08ffcef7731</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[portfolio-management]]></category>
            <category><![CDATA[strategic-planning]]></category>
            <dc:creator><![CDATA[Thiago Marquini Machado]]></dc:creator>
            <pubDate>Fri, 23 Oct 2020 10:55:21 GMT</pubDate>
            <atom:updated>2020-10-31T20:16:02.469Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Customer Epic #4 — Review</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItM9-YZIPLhFLkCj-xnCjQ.jpeg" /></figure><p>In order to bring the customer into the project management environment we need to look at a broader scenario within the company: we are talking about Portfolio Management.</p><p>The portfolio is the set of projects, programs, subsidiary portfolios and operations managed as a group to achieve strategic objectives. These various components compete for the limited resources available. The proportion of resources allocated to each is determined by organizational strategies and capabilities. Therefore, organizations must examine its unique circumstances and determine how to optimize and balance components.</p><p>Like projects and programs, the portfolio has a life cycle, but it has greater longevity and managerial attention. They can be terminated, merged and separated to achieve optimal performance.</p><p>They have an organizational scope that changes with the company’s strategic objectives. A project, a product line, an entire operation, can be terminated if they are no longer in accordance with those objectives, at a given time in the organization. This happens because valuable resources would be wasted on actions that no longer add the value that the organization needs.</p><p>On the contrary, other components like these can be added so that the strategic objectives of that time are achieved. Like a new unit in a new location targeting an unattended market, new products sold, new technologies developed, etc.</p><p>That is why Portfolio Managers must always be monitoring changes in the broader internal and external environments. They monitor strategic changes and add resource relocation, performance results and risks to the portfolio.</p><p>Program Managers and Project Managers linked to programs and projects subordinate to a portfolio must report to the Portfolio Manager, who in turn ensures the alignment and availability of resources for them.</p><p>The portfolio’s success is then measured in terms of its aggregate investment performance and the realization of its desired benefits.</p><p>While project and program managers focus on getting the job done right, portfolio managers focus on getting the right job done at the right time. That is, in order to achieve the company’s strategic objectives, determining, monitoring and providing conditions for the right projects, programs and operations to be conducted in the best way.</p><p>He is primarily responsible for ensuring that such projects, programs and operations that take place at the functional level deliver the expected benefits and materialize the business strategy determined at the executive level.</p><p>To do this, in addition to mastering project and program management practices and operational management, you must fully understand the business strategy, how it is defined and how it should unfold across all levels of the organization.</p><h3><strong>Principles of portfolio management</strong></h3><p>Portfolio management presents an organized approach to achieve strategic objectives:</p><p>· Efforts to achieve excellence in strategic execution;</p><p>· Increased transparency, accountability, sustainability and governance in general;</p><p>· Balance of portfolio value against general risks;</p><p>· Ensure that investments in components are aligned with the organizational strategy;</p><p>· Obtaining and maintaining sponsorship and engagement of senior management and key stakeholders;</p><p>· Active and decisive exercise of leadership by optimizing the use of resources;</p><p>· Foster a culture that embraces change and risk;</p><p>· Navigate complexity to enable successful results.</p><h3><strong>The life cycle and 6 performance domains of portfolio management</strong></h3><p>The Portfolio life cycle includes initiation, planning, execution and optimization. Good life cycle management by balancing stability and adaptability is the crucial managerial activity in today’s constantly changing environment.</p><p>Portfolio management divides its practices into six performance domains, which are addressed during its life cycle, namely:</p><p><strong>Strategic portfolio management:</strong> each component must be aligned with one or more strategic objectives, and the positive impact must be monitored constantly. This is achieved by a deep understanding of these objectives and how important each component is in relation to them. Any proposal to include a component should describe how it supports the achievement of the required business value;</p><p><strong>Portfolio governance:</strong> through open and transparent governance, including processes to categorize, prioritize, select and approve components, key stakeholders will be more likely to accept decisions and agree with the processes, even if they do not fully approve them;</p><p><strong>Portfolio capacity and capability management:</strong> the selection of components and the roadmap for their implementation is balanced between the organization’s current capacity and capability and the potential to bring in additional resources.</p><p><strong>Portfolio stakeholder engagement:</strong> active management of the engagement of key stakeholders is required. Being aligned and connected, the chances of delivering value increase. Active communication is the primary vehicle by which the exchange of information, improved transparency and stakeholder engagement are achieved;</p><p><strong>Portfolio value management</strong>: enables the investment to achieve the expected return as defined by the business strategy. The contribution and support of value needs to be monitored throughout the execution of the components as well as after their closure.</p><p><strong>Portfolio risk management:</strong> assesses risks at the portfolio level and considers how these risks impact the fulfillment of your strategic plan and the achievement of your objectives. It requires constant monitoring of the uncertainty that occurs inside and outside the organizational environment.</p><h3><strong>The customer and the portfolio management</strong></h3><p>So, once we have established that all of the company´s efforts must be aligned with a main strategical objective (or few objectives) in order to gather the desired benefits and value, we can place the customer on it.</p><p>Again, without a customer there is no project, operation or portfolio for you to manage, so we have to understand that <strong>there is no sustainable benefit and value attainment for the company if there isn´t any benefit or value to the customer.</strong></p><p>We may just have to add these customer benefits and value objectives to the company’s overall strategic objectives.</p><p>The <strong>customer is one of the key dimension of strategic planning</strong>. At the same time that we define what are our goals, we must be sure we are building an environment that is able to deliver the business value to the customer. The same business value that went to your canvas at the very beginning of the company or this cycle.</p><p>Never forget it.</p><p><strong>Ensuring that the customer is taken into account in strategic planning will make you think of him in every decision</strong>. If this is one of the main criteria for selecting portfolio components, we can be on the right track to really include the client in project management.</p><p>***</p><p>CLX Institute´s Growth Marketing course is at the same point of last week. Weird hair guy talking about heavy statistical marketing issues. This lesson has been particularly tough. And long…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b08ffcef7731" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Customer Epic #3 — Review]]></title>
            <link>https://thiago-marquini-machado.medium.com/the-customer-epic-3-review-67ed9f0903fe?source=rss-3d975c9d5369------2</link>
            <guid isPermaLink="false">https://medium.com/p/67ed9f0903fe</guid>
            <category><![CDATA[customer]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[customer-centricity]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[sales]]></category>
            <dc:creator><![CDATA[Thiago Marquini Machado]]></dc:creator>
            <pubDate>Sun, 18 Oct 2020 22:50:43 GMT</pubDate>
            <atom:updated>2020-10-31T20:04:26.971Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Customer Epic #3 — Review</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItM9-YZIPLhFLkCj-xnCjQ.jpeg" /></figure><p>So I started researching about the <strong>customer as the key stakeholder </strong>in Project Management and (guess what) couldn’t find anything.</p><p>I´m not surprised anymore.</p><p>Even in PMBOK, the most important guide on the subject, doesn´t even mention “customer” in its stakeholders management section.</p><p>That´s it. We develop all these projects for no reason. There is not a customer paying for it. There is not a client who will use it. The very person that is central to any project actually doesn´t matter at all.</p><p>In project management you are more likely to hear what the construction site dogs have to say (or bark) than what your client might want to say.</p><p>To hell with these customer guys!</p><p>Agile project management could be a little more customer-centric, but knowing these people the way I know, probably the product owner or whatever the customer´s voice within the company is it´s just another easy way of not having to talk to the real customer.</p><p>Great idea! Let´s pick a guy in our company, say he is the customer and we are fine. Just fine.</p><p>We came to the obvious conclusion that, apart from salespeople, <strong>nobody cares about customers</strong>. Once the sale is done, not even salespeople have to.</p><p>I really tried to come up with something myself. Stood in front of the whiteboard and made some scratches on the customer´s journey within the project, but is very hard to do so without any references.</p><p>However, we know that the way to include the client in project management is through stakeholder management. I sincerely believe that, although many tools and processes are the same for the client and for any other stakeholder, the client must be “managed” separately, as a whole other knowledge area.</p><h3><strong>Stakeholder engagement</strong></h3><p>Stakeholder is any individual, group or company that will be directly or indirectly impacted by the project, either positively or negatively. Because of this, he has a certain degree of interest, power, influence and impact over the project.</p><p>Having these attributes, a stakeholder can support or oppose a project, he can help it generate its benefits or he can try to prevent this from happening. He can be a factor of success or failure.</p><p>The client, the investor, the government, the affected population, the supplier, the consumer or the project team itself are stakeholders.</p><p>It is the role of the Project Manager to identify all stakeholders, define their degree of interest, power, influence and impact on the project and, from then on, plan strategies to engage them according to the best interests of the project.</p><p>Proper stakeholder engagement is crucial to success. You have no control over anyone’s will, so you cannot control stakeholders, nor their engagement, but you can create the right strategy in order to keep everyone’s level of engagement on its best level for the project.</p><p>Not necessarily all stakeholders should be fully engaged. Everything will depend on the degrees of influence, power, interest and impact of each one.</p><p><strong>Interest</strong>: it is the importance of the project for a given stakeholder. The customer is highly interested. But the company that runs the project may not be, if it is not strategically or financially advantageous. Or may have full interest, if this is crucial to business.</p><p><strong>Power</strong>: it´s the authority one have over the project. A director of the company that sponsors the project, a regulatory body for which the project needs endorsement or the client who hired the project has high power over it. An intern who works on the team or a consumer who doesn’t even know about it has low power.</p><p><strong>Influence</strong>: it is the extent to which an interested party can positively or negatively affect the project.</p><p><strong>Impact</strong>: the ability to make changes to project planning or execution. A client manager can try to change the scope of the project at all times and succeed due to his influence, but an operator who will operate the resulting product can try to change features to benefit himself and fail, as he does not even participate in meetings and has no influence.</p><p>If a stakeholder has a high interest and power over the project you want him to be your best friend, never your opponent.</p><p>For example, the Manager of a department is against the project to implement a system because it will change the whole way of working in that department and he does not agree. He may think that the system should have a certain tool that is not in scope and try by any mean to have it included, even if it is against a board decision. He will make your life very hard.</p><p>Therefore, you must collect all expectations and requirements of all stakeholder in the project, check the alignment with its objectives, identify the project risks related to each stakeholder and maintain the proper communication in order to try to keep him engaged in the best way.</p><p>Communication is necessary even to make it clear that some of the requirements are not part of the project and will not be. Notice what a delicate situation you have to manage.</p><p>If a stakeholder has little authority and interest in the project, you can only monitor him, as this status can change.</p><p>If he has little authority, but a lot of interest, you may want him to have the lowest possible engagement so that he does not negatively affect the project, because on the other hand, he can do little for helping you.</p><p>That is why all stakeholders must be identified. The engagement strategy will be planned later, but never neglect any of them.</p><p>In addition, you should always be monitoring communications and stakeholder engagement to see if the measures you take are being effective and adjust the strategy if it is not happening as you planned.</p><h3><strong>Conclusion</strong></h3><p><strong>The client is necessarily (and always is) the stakeholder who has greater power, interest, influence and impact on the project</strong>, many times greater than the executing company itself. In terms of management, no evaluation of these attributes is necessary. Everything is flashing red.</p><p>Therefore, I come here to make my manifest to all project management players:</p><p><strong>The customer is the main stakeholder</strong>. <strong>Don’t manage him like the others</strong>, get him out of this basket. Have a specific framework.</p><p>…</p><p>About the Growth Marketing CLX Institute minidegree program: it is now getting quite weird. There is this european dude with spiky hair teaching about some heavy statistics approach for marketing which I thought marketers would never be able to even understeand.</p><p>Interesting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67ed9f0903fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>