How to approach problem solving

Introduction

At its core, engineering revolves around a fundamental question: How do we solve problems? The key lies in breaking down a large problem into smaller, more manageable parts—a process often referred to as "map and reduce." We continue dividing the problem until each part is simple enough to handle individually.

Breaking Down Problems

This approach provides a clear roadmap of the problem's structure. While it may not offer an immediate solution, it highlights which components are crucial and which are less significant. It often reveals existing solutions for some parts, saving us from reinventing the wheel. Sometimes, just mapping out the problem brings us halfway to the solution.

Example: Building a House

Building a house might seem overwhelming at first glance. But when we break it down into tasks like laying the foundation, constructing walls, installing the roof, setting up plumbing and electrical systems, flooring, interior design, painting, and obtaining necessary permits, each task becomes more approachable.

Zooming in on the electrical work:

• Installing wiring in all rooms
• Identifying switch locations
• Setting up lighting and AC points
• Selecting appropriate hardware

A skilled electrical engineer can plan these details, making it a matter of purchasing materials and hiring an electrician. By dissecting the task, it no longer feels insurmountable. With expertise, skilled labor, and adequate funds, the problem becomes manageable.

Adaptive Challenges

Not all problems have ready-made solutions. Some require us to adapt and think differently—these are adaptive challenges.

Example: Designing for Diverse Needs

Imagine designing a house for a multi-generational family with varying needs and preferences. There's no standard blueprint for this scenario. You must:

• Engage with all family members
• Understand unique requirements (privacy, accessibility, functionality)
• Adapt the design accordingly

This process involves negotiation, empathy, and compromise. It's less about technical execution and more about addressing emotional and behavioral aspects. Adaptive challenges demand leadership, creativity, and the ability to navigate uncertainty.

Application in Software Engineering

The map and reduce principle is equally vital in software engineering.

Technical Problems

Many software tasks are technical problems with known solutions:

• Implementing a login feature using existing libraries
• Setting up a database using standard practices

With the right expertise, these tasks are straightforward.

Adaptive Challenges

However, adaptive challenges arise when:

• Building a platform for diverse user groups (patients, doctors, administrative staff)
• Balancing conflicting requirements and workflows
• Continuously refining the product based on user feedback

These challenges require:

• Engaging stakeholders
• Understanding unique needs
• Innovating and adapting solutions iteratively

Adaptive challenges in software engineering necessitate flexibility, stakeholder engagement, and a willingness to pivot as new information emerges.

Conclusion

By embracing the map and reduce principle, we can tackle both technical and adaptive challenges effectively. Breaking down problems simplifies technical tasks, making them manageable with existing expertise. Recognizing adaptive challenges prompts us to innovate, adapt, and approach problems with a fresh perspective.

Whether constructing a building, developing software, or solving complex organizational issues, understanding the distinction between technical problems and adaptive challenges is crucial. This awareness enables us to apply the right strategies, ensuring we address each challenge with the appropriate tools and mindset.