PM Thinking

In project management, strategic thinking, systems thinking, and design thinking each play important but distinct roles. All three approaches contribute to making projects more successful, focused, and sustainable.

 

 

Each mindset ensures in its own way that a project is not only executed but also better conceived, implemented more efficiently, and planned with greater sustainability.

​Strategic Thinking

Ensure long-term alignment and value for the company.

 

Key Aspects in Project Management:

• Align project goals with corporate strategy: Ensure projects contribute to strategic objectives.

• Stakeholder analysis and management: Engage stakeholders early and communicate purposefully.

• Project prioritization: Evaluate projects based on strategic relevance (e.g., using portfolio management).

• Strategic risk awareness: Assess how project risks impact the overall business.

 

Approach:

• Align Project Goals with Corporate Strategy: The company aims to increase customer loyalty and boost revenue through digital channels. Therefore, the app should offer features that enhance customer retention, such as personalized offers or quick support.

• Stakeholder Management: Conduct early discussions with key stakeholders (marketing, sales, IT, etc.) to ensure all relevant perspectives are considered.

• Prioritization and Budgeting: The app is regarded as a strategic project and is given the necessary priority. At the same time, the budget and resource requirements are determined based on the project’s importance to the company’s strategic objectives.

• Risk Management: Identify potential risks, such as market risks (competitive pressure) or technical risks, and develop corresponding mitigation plans.

​Systems Thinking

Understand interconnections and interactions within the larger overall system.

 

Key Aspects in Project Management:

• Holistic Perspective: View projects not in isolation but within the context of the organization, processes, technologies, and people.

• Recognize Interdependencies: Anticipate the impact of project decisions on other projects, departments, or systems.

• Consider Dynamics and Feedback Loops: For example, in cases of resource constraints or process changes.

• Actively Practice Change Management: Understand how changes affect the entire system.

 

Approach:

• System Analysis and Process Integration: The team analyzes how the mobile app must be integrated into existing systems (e.g., CRM, e-commerce platform). The impact on other departments such as customer support and logistics is also taken into account.

• Recognizing Interdependencies: If the app offers personalized promotions, it needs to communicate with data from the CRM system. This requires coordination between different departments and IT systems to avoid errors or inefficiencies.

• Establishing Feedback Loops: How does the system respond to changes? Is the app well received? Are there positive or negative feedbacks that should influence the design? These insights feed into ongoing development (change management).

• Change Management: The project team considers how the app’s introduction will alter existing processes (e.g., support teams must be able to handle related inquiries) and develops strategies to prepare employees for these changes.

 

​Design Thinking

Develop user-centered solutions creatively and iteratively.

 

Key Aspects in Project Management:

• Focus on User Needs: Capture requirements not only from a technical perspective but primarily from the end user’s point of view. We take the customer seriously.

• Promote Iterative Approach and Prototyping: Develop, test, adapt, and improve in phases. The hybrid approach - combining the best of sequential and agile methods - has proven highly effective.

• Interdisciplinary Collaboration: Bring together teams from different specialties.

• Openness to New Ideas: Allow even “out-of-the-box” ideas to foster innovation.

 

Approach:

• Empathy Phase: The process begins with engaging potential users (e.g., through interviews or surveys) to understand their needs and pain points. Typical questions might include: “What frustrates you most about existing apps?” or “What features would you like to see?”

• Problem Definition: Based on the insights gathered during the empathy phase, the main problem is clearly defined - for example: “Our users need an easy-to-use app that delivers personalized offers in real time.”

• Ideation: In creative workshops, a wide range of potential solutions and ideas are generated. The team also welcomes unconventional ideas to foster innovation (e.g., integrating augmented reality for a unique shopping experience).

• Prototyping: An initial prototype is developed, containing only the core features. This version is tested with a small group of users to gather feedback and continuously refine the app.

• Testing: The prototype is further improved based on testing outcomes. Ongoing feedback loops are essential to ensure that the design truly meets the users’ needs.