Chapter 2: Selecting the Customer, Market, or Internal Challenge
A credible digital transformation achievement story begins before the technology is introduced. It starts with a clearly defined problem, limitation, risk, or unmet need. Without this foundation, readers and evaluators may understand what a provider delivered but not why the work was necessary, difficult, or valuable.
Technology providers, consulting firms, systems integrators, managed service providers, digital agencies, and implementation partners should therefore document the conditions that existed before their intervention. The challenge provides the context against which actions and results can be evaluated.
Identify One Principal Challenge
Transformation initiatives frequently address several related problems. A customer may be dealing with outdated systems, rising operating costs, security vulnerabilities, inconsistent data, slow service, limited scalability, and poor user experiences simultaneously. Although these issues may all be relevant, an achievement story becomes difficult to follow when it treats every concern as equally important.
Select one principal challenge that connects directly to the principal achievement. Supporting challenges can be included when they clarify the project’s complexity, but they should not obscure the central problem.
For example, the main challenge might be an inability to process customer requests within acceptable timeframes. Outdated software, manual approvals, disconnected databases, and staffing limitations may explain the problem, but the delayed service remains the central challenge.
Establish Baseline Conditions
A baseline records performance before the solution, service, or intervention was implemented. It creates a credible point of comparison for demonstrating improvement.
Depending on the project, baseline measures might include:
- Average processing or response time
- System availability and interruption frequency
- Operating or infrastructure costs
- Error, defect, or rework rates
- Security incidents or unresolved vulnerabilities
- Customer satisfaction or abandonment rates
- Employee hours devoted to manual tasks
- Sales conversion, retention, or adoption rates
- Energy consumption, waste, or resource use
A claim that a system became “faster” or “more efficient” has limited meaning without an initial condition. A statement that processing time decreased from four days to six hours is more specific and verifiable.
Providers should record where baseline figures came from, how they were calculated, which period they cover, and whether the customer approved their use.
Understand the Full Range of Constraints
Digital transformation rarely occurs under ideal conditions. A strong achievement narrative explains the constraints that increased the difficulty or importance of the work.
Operational constraints might include the need to maintain uninterrupted service while replacing critical systems. Technical constraints could involve incompatible applications, poor-quality data, limited infrastructure, or complex integration requirements. Financial constraints may include fixed budgets, uncertain returns, or the cost of maintaining legacy technology.
Security and privacy obligations may restrict how information can be stored, transferred, or analyzed. Workforce constraints can include limited technical skills, resistance to change, distributed teams, training requirements, or shortages of qualified personnel.
These details should not become excuses. Instead, they help explain why the provider’s decisions, expertise, and actions were significant.
Document Legacy and Process Problems
Legacy systems can remain operational for years while gradually creating cost, risk, and complexity. They may be difficult to update, dependent on unsupported technology, vulnerable to security threats, or unable to exchange information with newer platforms.
Disconnected processes create additional problems. Employees may have to enter the same information into multiple systems, reconcile inconsistent records, rely on spreadsheets, send manual approvals, or search across separate databases. Customers may be required to repeat information or wait while departments coordinate behind the scenes.
An effective digital transformation solutions story documents these conditions in understandable language. Rather than focusing only on technical architecture, explain their real consequences: delayed decisions, unnecessary labor, inconsistent experiences, lost revenue, increased risk, or limited access to services.
Protect Confidential Customer Information
Providers need sufficient context to establish the challenge, but they should not reveal confidential, personal, proprietary, regulated, or security-sensitive information without authorization.
When a customer cannot be identified publicly, the provider may describe it appropriately, such as “a regional healthcare network,” “a national financial services organization,” or “a manufacturer operating across five facilities.” Sensitive financial figures may sometimes be expressed as percentages, ranges, indexed values, or other approved measurements.
Anonymization should not be used to disguise unsupported claims. Providers should retain internal evidence and obtain necessary customer, legal, privacy, security, and communications approvals before publishing information or submitting it for recognition.
Separate the Customer’s Challenge from the Provider’s Challenge
The customer’s challenge explains the need for transformation. The provider’s challenge explains what made delivering the solution difficult.
For example, a retailer’s challenge may have been inconsistent inventory information across its stores and online channels. The systems integrator’s challenge may have been connecting several legacy databases without interrupting transactions during a peak sales period.
Both perspectives can strengthen the story, but they should remain distinct. This distinction also supports appropriate attribution by showing what the customer needed and what the provider specifically accomplished.
Demonstrate Scale, Complexity, and Significance
Scale is not limited to company revenue or the number of countries involved. It may be demonstrated through users served, systems connected, records migrated, facilities covered, transactions processed, risks addressed, or communities reached.
Complexity may arise from regulatory obligations, demanding timelines, diverse stakeholders, multilingual environments, accessibility requirements, cybersecurity concerns, or dependence on uninterrupted services.
Significance explains why solving the problem mattered. Did the challenge affect essential public services, customer trust, employee safety, business continuity, financial sustainability, competitive performance, or access for underserved users?
Agree on Performance Measures Early
Whenever possible, the provider and customer should select performance measures before implementation. Agreed measures reduce the temptation to choose only favorable statistics after the work is completed.
Each measure should have a defined baseline, calculation method, timeframe, source, owner, and target. Both parties should also clarify which outcomes can reasonably be attributed to the solution and which may have been influenced by other changes.
A clearly defined challenge creates the foundation for a persuasive digital transformation achievement. By connecting that challenge to organizational, industry, customer, community, or public value, providers can show not only that technology changed—but why the transformation was worth achieving.