Just Log a Ticket

Let’s look at Juan.

He is a regional director who wants to introduce a new data-driven culture. Starting next month, he wants all five of his team leads to extract their own weekly performance metrics from the company's central reporting system to discuss in their Monday meetings.

Juan has had full admin access to this system since the day he was hired. Because it was set up for him by default, he assumes everyone at the leadership level has the same access. He prepares the rollout email explaining the new reporting rhythm.

Making assumptions often saves you time but it can waste much of your team’s time if they turn out to be incorrect.

Nobody had access. When they tried to log IT tickets there weren't clear options of what to select to get the right system, so they logged generic tickets. It took days of back and forth before the right access could be provided to the system that allowed the reports needed.

If Juan had spent the time to check the access and provide instructions the team would have had access that day as IT had actually automated the approval for that application. The reason nobody could find it was because the name people call the database is not its official name. Juan would have learned this when he asked IT.