Not only that we spend just a view hours to come up with the first results, we also used Power Platform components to collect feedback and improve our POC solution by asking our spare-partners interviewed earlier on what impact this new setup would have. We looked after quick wins and finally we decided to go with theseĬonnectivity options to build a POC. Neither should Microsoft Teams user being forced to learn SAP GUI to collaborate with SAP teams. As an example: SAP Fiori users shouldn’t be blocked or forced to use a different technology for accessing apps. With the insights collected and our customer journey map outlining the as-is situation we came up pretty fast with a SWAT analysis that later on we used to draw above visual as the new to-be situation and overall goal to aim for.īut we didn’t stop there and challenged us again using SCAMPER methodology to go beyond and look after things we might overlooked, but those should be considered for a better overall solution.
So we started by interviewing both parties from SAP- as well as from Microsoft Technology side and collected insights that we then used to setup a customer journey map. The challenge was around what would be the next level of better interacting as a team, so far using different technologies. Obviously, as in design thinking mode, our mission was not about creating a specific app, process or implement a solution. In a recent design thinking workshop we challenged ourselves taking processes to the next level and try imagining how both technologies could come together in action, benefit from and even taking each other to the next level. Your digital transformation journey is ongoing and you’re just about reimagine your next level of transformation – have you considered Power Platform being part of it? Assuming you’re using both SAP- and Microsoft Technology.