In this week's episode, Ricardo talks about the difference between compliance and conformity. Compliance and conformity are rules that an organization must always follow. However, the purpose of each is quite different. Often the company decides to follow a specific rule not because it has to but because it is good for the business, such as obtaining ISO certification.
In this week's episode, Ricardo talks about availability bias. He explains that when a risky event is repeatedly exposed on the news or by a group of people next to us, our perception is altered by that exposure, which often makes us lose rationality about the real probability or impact. One of the examples is the panic seized by the delay of flights all over the world.
In this week's episode, Ricardo talks about the potential applications of artificial intelligence in projects and compares the different impacts and implementation complexity of each of them. He comments that a project that is self-managed in all dimensions by Artificial Intelligence will have a tremendous impact on both the people involved in the project and the project itself.
In this week's episode, Ricardo talks about the three central values that project management brings to the organization that you could talk about in a brief speech in an Elevator Pitch. The first: Project management is one of the most powerful tools to organize your workflow and prevent chaos from setting in. Regardless of the approach used, project management will define the criteria that will manage the flow of work within the organization.
In this week's episode, Ricardo talks about the latest news published in the press about the streaming service Netflix, which, upon announcing the first reduction in the number of subscribers to the platform in the last ten years, suffered a devastating drop in the value of its shares. Netflix's value dropped from more than 300 billion dollars at the end of 2020 to 89 billion after the announcement.
In this week's episode, Ricardo returns to the concept of Antifragile, presented by Nicholas Taleb in his book, where Taleb stated that the antifragile "is not necessarily the opposite of fragile" but "what improves with shock." Ricardo talks about making the different types of systems antifragile, systems that can be you, your career, or your company. He complements the concept and outlines the five steps from fragile to antifragile.
In this week's episode, Ricardo talks about the concept of Antifragile, presented by Nicholas Taleb in his book. To better explain it, Ricardo explains the meaning of being "fragile" and "robust," where "robust" is not necessarily the opposite of fragile. Robust refers to the ability to resist shock and is not necessarily improved by shock. What improves with shock is Antifragile. And what you gain from stress.
Ricardo recently watched, using his project management perspective, the documentary "Fyre - The Great Event That Never Happened," which was recommended by a friend. Fyre was supposed to be one of the music festivals that was supposed to be one of the most exclusive globally and ended up being a complete fiasco. The initial idea was to create an event to promote the celebrity booking application called Fyre.
Faced with this week's events with Russia's invasion of Ukraine, Ricardo had decided not to record any new episode this week. However, today he decided to record a different episode, talking about empathy and support in uncertain times like the current ones. In this week's episode, he talks about the importance of understanding that reality has changed and that there is no perspective on how the subsequent events will unfold.
In this week's episode, Ricardo talks about the exponential growth of problems in the project. He explains with several examples what exponential growth is, such as the behaviour of social networks when a post is shared with ten people and that each one will share with another ten people. So on, the number of views has a massive growth. We often rely on intuition to make a future prediction, imagining linearity.
This week's episode is super special, with Ricardo talking about the launch of the James Webb Telescope, scheduled for December 24th. He explains that the project to build this telescope is extremely complex (we haven't found an even bigger term to describe how complex the project is). And for a project of this size, the level of competence of the professionals involved doesn't matter.
In this week's episode, Ricardo explains the difference between agility and agile methods. He says that if the project uses an agile method, it may not necessarily have agility. And on the other hand, a project that uses the predictive model may have agility. Ricardo comments that, regardless of the method used, it is first necessary to have a critical sense of urgency, agility and adaptability in the organization.
Ricardo talks about affinity diagrams in this week's episode and how this technique can help you and your team organize ideas. He explains that when structuring a process, the scope of a project, risks, and other ideas, we usually create groups and distribute information within these groups. We will think differently using the affinity diagrams; first, we will have the pictures and then group; it is like an EAP in reverse.
This week we return to the theme from a few weeks ago, how technology projects are riskier than most people imagined. Surprised by the paralysis of Facebook, Instagram, and Whatsapp, we were more than left out of communication. The damage caused throughout the world by the hours out of the air on these platforms is incalculable. What to learn from what happened? How to deal with this dependence on companies today?
In this week's episode, Ricardo talks about the importance of having clear criteria as a reference when we evaluate a project. He explains that people's perception is different, and if we create a personal reference, it will have a different interpretation. Ricardo shows many examples of not explicit references, and besides that, the evaluation for these criteria will generate ambiguity. He also shows examples of detailed references.