Making Your Sprints More Insightful

24 Jul 2017 | Tags: , , , , , | Posted by Doug Rose

In my two previous posts, “Building a Data Science Life Cycle” and “Conducting Data Analytics in Sprints,” I present a six-stage framework to structure the work a data science team performs and five techniques for performing the work in intense, two-week cycles called “sprints.” These techniques go a long way to making the data science team productive.

In this post, I call your attention to several pitfalls that commonly undermine the data science team’s efforts, and I provide guidance on how to be proactive in avoiding these pitfalls. Generally, your data science team needs to squash anything that limits their mission to something other than exploration and discovery.

Change the Organization’s Mindset

Many organizations create data science teams and then essentially tie their hands, preventing them from truly exploring the data. Much less frequently, organizations provide their data science teams with too much freedom, so the teams end up chasing data and questions that are irrelevant to the organization’s success or getting so wrapped up in routine chores, such as managing the data warehouse, that they fail to produce anything of value. In most organizations, though, the problem involves a strict hierarchy that tries to control what the data science team does, and that is a formula for failure.

Prior to installing a data science team, an organization often must change its mindset and values. It must embrace a spirit of creativity and innovation, especially in respect to its data science team. When the team is doing what it should be doing, it is learning and helping the organization learn. It is discovering what the organization doesn’t know. Attempts to micro-manage the team run counter to its mission.

However, the data science team does need to deliver value. It should serve the needs of the organization. Data science teams can achieve that goal by being highly service-oriented and by collaborating with everyone across the organization to get their questions answered, help them overcome any challenges they face, and inform their decisions.

Work without Objectives

Most organizations still view work as a series of goals and objectives. They invest a great deal of time, money, and effort on planning, management, and compliance. Teams are expected to set goals in advance, formulate plans to meet those goals, execute their plans, and deliver the promised outcomes. While that approach works well for most teams, it is counterproductive for data science teams whose mission it is to explore and innovate. Data science teams need to follow the data and the questions, and they cannot shift direction if their path is carved in stone.

If you’re on a data science team, you may feel as though your team is trying to hit a constantly moving target. Every sprint introduces new questions that may lead the team in a different direction. Sometimes, the team may not even know what the moving target is. The team may be looking for patterns in the data that reveal new targets. By working without objectives, the team has the flexibility it needs to let its curiosity and the data determine the outcomes.

Take Advantage of Serendipity

Serendipityis a happy happenstance, such as striking up a conversation with the CEO of Microsoft at a Mariners game and having him offer you a job on the spot. It is an odd concept in the world of business, where strategy, goals, objectives, and planning are enshrined as the essential components of success.

However, more and more evidence points to the advantages of serendipity over goal setting and planning. One of the best books on the topic is Why Greatness Cannot Be Planned: The Myth of the Objective,by Ken Stanley and Joel Lehman. According to the authors, “Objectives actually become obstacles towards more exciting achievements, like those involving discovery, creativity, invention, or innovation.”

Data science teams are wise to capitalize on serendipity. For example, if a team member sees something unexpected and intriguing in the data the team is analyzing, the team needs to follow up on that discovery. You don’t want your team focused on objectives at the expense of overlooking a groundbreaking discovery. Professor Stanley calls these “stepping-stones” — interesting things that eventually lead to insights. If you ignore them, you are likely to miss key discoveries.

Deliver Practical Knowledge and Insights

When you’re working on a data science team, it’s easy to get so caught up in the data, analysis, exploration, and discovery that you lose sight of the organization’s needs. Driven by innate curiosity to follow wherever the data leads, the team forgets that others in the organization are relying on it to deliver knowledge and insight that guide strategy and inform decision-making. Every couple weeks, the team delivers its reports or presentations, which the team finds fascinating but which leave everyone else in the organization wondering “So what?” or “Who cares?”

To avoid this pitfall, the data science team must engage, to some degree, in guided exploration. Three tools in particular are helpful for structuring and guiding the data team’s work:

  • The data science life cycle (DSLC), described in my previous post, “Building a Data Science Life Cycle (DSLC).”
  • A question board that encourages everyone in the organization to post their questions, concerns, and challenges for the data science team to address.
  • Storytelling, which forces the team to present its findings in a context relevant to the organization’s mission and specific needs.

Focus on Exploration over Routine Work

By its very nature, routine is repetitive, and it can become hypnotic, lulling you into a complacency that prevents you from noticing the wonderful world that surrounds you. The same is true for a data science team. It can become so wrapped up in capturing, cleaning, and consolidating data and creating data visualizations that it loses its sense of adventure. It falls into a rut and stops asking interesting questions. When looking at the data, it may not even notice an intriguing fact that’s staring right back at them.

To avoid this pitfall, try the following techniques:

  • Use a question board to gather questions, concerns, and challenges from across the organization. Otherwise, the data science team’s workspace is likely to become an echo chamber in which the team members merely reinforce one another’s work.
  • Add stakeholders from across the organization to the data science team on a temporary basis to share their unique perspectives and challenge the team.
  • Ask more interesting questions. If you find that your team is asking mostly Who?, What?, When?, Where?, How?, and How much? questions, try asking more Why? and “Why not? questions. Factual and quantitative questions are important, but be sure to ask questions that force the team to think about causation and possibilities.

Keep in mind that your data science team should be committed to exploration, discovery, and innovation that’s relevant to the organization’s needs. If the team works toward achieving that mission, it will be less susceptible to the most common pitfalls.

Back to Posts