What Not How: The Rules Approach to Application Development

The "What Not How" approach to application development focuses on defining the desired outcomes and functionalities of an application without delving into the specifics of implementation. This methodology contrasts with traditional development approaches, which often emphasize how to achieve specific functionalities. By concentrating on the "what"—the goals, user needs, and overall vision—developers can foster more innovation, adaptability, and alignment with user expectations. This article explores the key principles of the "What Not How" approach, its benefits, and practical strategies for incorporating it into development practices.

Understanding the "What Not How" Approach

The "What Not How" approach is grounded in the principle that defining what needs to be accomplished is more crucial than specifying how to accomplish it. This approach encourages a focus on the end goals rather than the methods of achieving those goals. This shift can lead to more flexible and innovative solutions, as it allows developers to explore various ways to meet user needs without being constrained by predefined methods.

Key Principles

1. Outcome-Oriented Thinking
   By emphasizing what the application should do rather than how it should be built, teams can concentrate on solving problems and delivering value to users. This principle helps in setting clear objectives and measuring success based on user satisfaction and achievement of business goals.

2. Flexibility and Adaptability
   Focusing on the desired outcomes rather than the implementation details allows for greater flexibility. Development teams can adapt to new technologies and methodologies as they emerge, without being locked into specific approaches that may become obsolete.

3. Encouraging Innovation
   When developers are not constrained by specific how-to instructions, they are free to explore creative and innovative solutions. This can lead to more effective and unique applications that better address user needs and market demands.

4. Clear Communication
   Defining what needs to be done helps in clear communication between stakeholders, developers, and users. It ensures that everyone is aligned on the objectives and expectations, reducing misunderstandings and enhancing collaboration.

Benefits of the "What Not How" Approach

1. Enhanced Focus on User Needs
   By prioritizing what the application should achieve, developers can create solutions that are more aligned with user needs and expectations. This user-centric approach often results in more intuitive and effective applications.

2. Improved Project Flexibility
   The approach provides room for adjustments and changes throughout the development process. As new insights or technologies emerge, the development team can pivot and refine the solution without being constrained by a rigid implementation plan.

3. Increased Innovation
   With fewer constraints on how to build the application, developers are encouraged to experiment with new ideas and technologies. This can lead to more innovative solutions and a competitive edge in the market.

4. Simplified Requirements Gathering
   Focusing on what needs to be accomplished simplifies the requirements gathering process. Stakeholders can more easily communicate their needs and expectations, and developers can better understand and address them.

Implementing the "What Not How" Approach

1. Define Clear Objectives
   Begin by clearly defining the objectives and desired outcomes of the application. This includes understanding user needs, business goals, and any specific constraints or requirements that must be met.

2. Encourage Open Exploration
   Allow development teams to explore various methods and technologies to achieve the defined objectives. Encourage creativity and experimentation to find the best solutions.

3. Maintain Flexibility
   Be prepared to adapt and adjust as new information or technologies become available. Maintain a flexible approach to development that prioritizes achieving the objectives over sticking to a predefined method.

4. Regularly Review and Refine
   Regularly review the progress and outcomes of the application development process. Ensure that the objectives are being met and make refinements as needed to improve the application and address any emerging needs.

Conclusion

The "What Not How" approach to application development shifts the focus from the specifics of implementation to the desired outcomes and goals. By prioritizing what needs to be achieved, this approach fosters innovation, adaptability, and a stronger alignment with user needs. Implementing this methodology can lead to more effective and user-centric applications, ultimately contributing to greater success in the competitive software market.