It’s Friday afternoon, you receive an email about the flagship system everyone was excited with, which went live on Monday. There are problems; the system is not responding quickly enough, and we are losing sales. Have you got a “few minutes” to help?….In other words, would you like a long weekend?
Your system needs urgent changes to make it work. Turning up the dials can only take you so far.

Unsurprisingly, redesigns are needed as the system is not scalable. Turns out, testing performance is not the same as a scalable system in real life. And your stakeholders never understood that.

Now the fate of the system lies in your hands.

This session is about approach and guidance, not the nitty gritty code. Ok, there is some of that too... We will look at examples of how and why these issues happen, and how to avoid them. Not only will you get tactical “sticky plasters”, but also strategical redesign tips. After all, you need to spot early on the red flags in the requirements, because cutting corners can cost dearly in the long run. And the best part? This is applicable to Power Platform, Azure stack and bespoke systems