The Clearly Podcast

Debunking Best Practice

Summary

In this podcast, the hosts discuss the concept of best practices in IT consulting and why they often need to be debunked. They highlight that clients frequently seek a definitive list of best practices, expecting these to be universal guidelines for tasks such as building databases or setting up environments. However, the hosts argue that best practices are highly situational and can be constraining if followed blindly.

The term "best practice" is considered misleading, as what is deemed best practice can change over time and is context-dependent. Clients often find comfort in the idea of best practices, seeing them as a way to de-risk their projects. However, the hosts emphasize that blindly following supposed best practices can actually increase risks rather than mitigate them.

They discuss how to handle client inquiries about best practices by explaining that there isn't a one-size-fits-all solution. Instead, they focus on scenario planning and providing preferred options based on the specific needs of the client. Transparency about the options and trade-offs is crucial for building trust and achieving better outcomes.

The conversation also touches on the allure of new technologies and features still in preview. While these can be tempting, it’s important to balance the excitement with the practicalities of using untested features and understanding the associated risks.

In conclusion, the hosts agree on the importance of having mature, informed discussions with clients to tailor solutions to their specific needs, rather than following generic best practices. They also decide to plan their podcast topics in advance for better organization and end on a light note, humorously assuring listeners that they are fully clothed.

You can download Power BI Desktop from here.

If you already use Power BI, or are considering it, we strongly recommend you join your local Power BI user group here.

Transcript

Andy: Welcome to our podcast. How are you both doing today?

Tom: I'm good, thanks. How about you?

Andy: I'm well, though it's a bit cold here in Texas.

Shailan: All good. By the way, just for our listeners, no, we're not doing this podcast naked.

Andy: Definitely not. Today's episode is the first of our book series, where we'll tackle different chapters in no particular order. We'll start with debunking best practices, a topic we often discuss.

Tom: There's often an expectation from customers that there's a definitive list of best practices. They might ask, "What's best practice for building a database or setting up an environment?" But in reality, best practices are highly situational and can be constraining if followed blindly.

Andy: How do you handle clients asking for best practices? Do you just use common sense and your expertise?

Tom: I start by explaining that best practices don't exist in the way they think. There's no universal handbook. The idea of best practices can be misleading because it often discourages considering alternative, potentially better approaches for specific situations.

Andy: Is the term "best practice" misleading?

Shailan: Absolutely. It's often scenario-based. What was considered best practice years ago, like data aggregation, might not be necessary now with more resources available. So, what's considered best practice depends on the context.

Tom: Exactly. Even years ago, the idea of a single best way to do something wasn't always accurate. It’s about adapting broad principles to specific situations.

Andy: Do clients find comfort in the term "best practice"?

Shailan: Yes, it gives them a sense of following a proven path. But following so-called best practices can make you average, not the best. It’s about comfort and reassurance more than actual effectiveness.

Tom: Clients often want a clear, unquestionable guideline to avoid making wrong decisions. But blindly following supposed best practices can actually increase risks rather than mitigate them.

Shailan: I've had clients ask for best practices, especially with new technologies like cloud adoption. I explain that best practices are situational. We discuss different scenarios and provide a preferred option, rather than a one-size-fits-all solution.

Tom: Being transparent about options and trade-offs is crucial. You need to tailor solutions to each client's specific needs.

Andy: So, how do we discuss this with clients who want best practices to de-risk their projects?

Shailan: We explain that there might not be a universal best practice for their situation. Scenario planning helps them understand the options and choose the most suitable approach.

Tom: Exactly. It's about understanding the risks and being clear that some so-called best practices might not be the best fit for them. Mature conversations about these decisions lead to better outcomes.

Andy: Agreed. It’s about making informed decisions rather than blindly following guidelines.

Shailan: Also, clients sometimes want to use new features still in preview. It's about balancing the allure of new tech with the realities of using something not fully tested.

Tom: There are times when using beta or preview features is necessary, but it’s crucial to understand and communicate the risks involved.

Andy: Right. We need to be cautious and make sure everyone understands the potential implications of using new, unproven features.

Tom: Having mature, informed discussions with clients helps them understand why certain decisions are made, which builds trust and leads to better outcomes.

Andy: Absolutely. That’s a wrap for this topic. Let's decide on the next podcast topic in advance to stay organized.

Shailan: Sounds good. Let’s make it part of our routine.

Andy: Great. For our next topic, we'll discuss "seduction" by new technologies and how to handle it, a follow-up to today's discussion.

Shailan: And to end on a light note, yes, we are fully clothed.

All: (Laughter)