DynamicsDad here, ready to dive into another topic: using design thinking principles while working with our users in D365 Finance and Operations (F&O). I recently went through a college course on Design Thinking through Northwestern University and I highly recommend doing this (or just read today's blog) as it helped me gain an alternative way to solve problems.
If you've ever felt like you're solving the wrong problems or missing the mark with user expectations, this one's for you.
What is Design Thinking?
Design thinking is a user-centric approach to problem-solving that emphasizes understanding user needs, prototyping, and iterative testing. It's about putting yourself in the user's shoes and designing solutions that truly meet their needs.
"Think of it like planning a family vacation; you wouldn't just book the first hotel you find; you'd consider everyone's preferences, budget, and the best way to keep the kids entertained."
Key Principles of Design Thinking:
Empathize: Understand the user's needs and challenges.
Job to Be Done: Understand the underlying job that users are trying to accomplish.
Define: Clearly articulate the problem you're solving.
Ideate: Brainstorm a range of possible solutions.
Prototype: Create a tangible representation of one or more ideas.
Test: Gather feedback and refine the solution.
Dad Example: Planning a Family Vacation
Let's break it down with a classic dad scenario – planning a family vacation.
Empathize: Talk to the family and understand what everyone wants. The kids might want a theme park, while your spouse might prefer a relaxing beach.
Job to Be Done: Ensure the vacation provides both entertainment and relaxation, fulfilling the core need of a memorable and enjoyable family experience.
Define: The problem is planning a vacation that balances fun for the kids and relaxation for the adults.
Ideate: Brainstorm possible destinations that offer both. Consider places like Orlando (for theme parks) or a resort that has activities for kids and a spa for adults.
Prototype: Create a basic itinerary, showing how you can split the days between theme park fun and beach relaxation.
Test: Share the itinerary with the family and gather feedback. Adjust based on their input to ensure everyone is excited about the trip.
Applying Design Thinking in D365 F&O
Real-World Example: Improving Purchase Order Processes
Let's take a closer look at how to apply each step of the framework to improve the purchase order process in D365 F&O.
Empathize:
Conduct detailed interviews with all stakeholders involved in the purchase order process. This includes warehouse staff, the procurement team, suppliers, and financial analysts. Observe their workflows and take note of pain points.
Findings: Warehouse staff spend too much time manually updating purchase orders. The procurement team struggles to track order statuses, leading to delays. Financial analysts lack real-time data for accurate reporting.
Job to Be Done:
Throughout the process, keep the fundamental job that users are trying to accomplish at the forefront. For the purchase order process, this job is to streamline and automate updates to save time, reduce errors, and provide real-time visibility into order statuses.
Example: The mobile app and integrated dashboard should focus on making the purchase order process more efficient and reliable, addressing the core needs of each user group involved.
Define:
Clearly define the problems based on your findings.
Problem Statement: "The current purchase order process is inefficient due to manual updates, lack of real-time tracking, and insufficient data for reporting."
Ideate:
Facilitate brainstorming sessions with your team to come up with innovative solutions. Encourage creative thinking and consider a wide range of ideas.
Ideas Generated:
A mobile app for real-time purchase order updates.
Automated notifications for order status changes.
An integrated dashboard for tracking purchase orders and generating reports.
Prototype:
Select the most promising ideas and create prototypes. These should be simple representations that can be quickly developed and tested.
Prototype Created: Develop a basic version of the mobile app that allows warehouse staff to update purchase orders in real-time. Include features like barcode scanning and automated notifications.
Test:
Present the prototype to the users and gather their feedback. Iterate based on their suggestions to refine the solution.
Testing Phase:
Warehouse staff test the mobile app and suggest improvements, such as adding voice command features and integrating with existing inventory systems. Procurement tests the automated notifications and provide feedback on the frequency and format.
Final Iteration:
Incorporate the feedback and develop a more refined version of the mobile app and notification system. Ensure the solution integrates seamlessly with D365 F&O and addresses all user needs.
See? It's just that easy. Kidding (mostly). Remember... with any framework, they're meant to sound easy. They become easy with practice. And yes, I'm talking about practice (Ted Lasso reference). This is where you apply another framework, Learn, Do, Teach. You've learned this, now do it (use it), and learn it enough to teach it to someone else.
Dad Joke (comment on LinkedIn if you skipped all the way down here)
Why do turkeys play percussion? They have drumsticks.
DynamicsDad out!
Comments