The Limestone Protocol: How to Modernize Your Tech Stack in Six-Week Sprints

Step 1: Identify the highest-impact business problem

Before organizations think about the data issues they need to tackle, they should determine the most important business problems facing their stakeholders.

Drawing from his experience at Limestone, David shares that 87% of companies misdiagnose their data problems, focusing on symptoms rather than root causes.

The method for uncovering the right problem involves:

• Interviewing key stakeholders
• Identifying the tasks they can’t perform
• Triaging their limitations based on the greatest business risk

David advises, “Change the word ‘data’ to the actual name of the type of stakeholder and the exact thing they can't do today. That's the project.”

For example, a company might uncover that its financial analysts can’t generate reconciliation reports without engineering support, preventing them from making informed decisions in a timely manner.

Step 2: Divide underlying data issues into components that can be addressed in six weeks

By identifying high-impact business problems, organizations can focus on the most pressing underlying data issues and begin to understand how exactly they need to be tackled.

However, organizations should divide the issue into components that can be addressed in just six weeks. For example, rather than overhauling all data pipelines at once, they could focus on the single pipeline that's blocking their most critical weekly report — an issue that can typically be fixed in three to four weeks.

This enables organizations to gain immediate return on investment in modernization, building buy-in for broader transformation efforts while ensuring they’re geared toward meeting true business needs.

Step 3: Configure flexible, replicable architectural components

Warning: 60% of companies build solutions that can't scale. 

While organizations should be focused on meeting immediate needs in a six-week sprint, this shouldn’t come at the cost of future adaptability.

From data pipelines to API architecture, the architectural components they configure in a sprint should be flexible and designed to be replicated for other use cases.

David highlights that organizations don’t need to spend a significant amount of time deliberating about what might be required in the future, noting that 20% of their effort at the sprint stage will reveal the majority (80%) of future accommodations that need to be made.

For example, David and his team at Limestone Digital spent six weeks fixing a client’s inventory reporting. “By week three, we'd uncovered 80% of their data quality issues and integration needs,” he says. “Not through interviews and workshops, but by touching real data and seeing what broke.”

Step 4: Immediately plan the next six-week sprint to drive continuous improvement

Organizations should maintain a strict commitment to the six-week timeline, even if it means reducing the scope. This will help avoid delivery gaps that disrupt long-term momentum. Once complete, they should immediately begin planning the sprint, using insights from their most recent one to determine their priorities for the next.

Establishing this predictable rhythm of continuous improvement is critical, as it helps increase organizational trust in modernization at large. It also provides a valuable opportunity for leadership and implementation teams to better understand the relationship between different data points and broader business objectives. 

Limestone’s 72% pilot-to-expansion rate reveals how David’s approach helps build lasting momentum.

“Drive continuous improvement,” David notes. “When you look back on a six-month period or a one-year period, you’ll just see win after win after win.”