Remove Approval steps!
I always hear that they are really needed. Really?
Give more trust to the employee.
Trust that the employee does the right thing for the customer and the company.
What if it goes wrong? What is the worst case scenario that could happen? What is the chance this could happen? Can you revert it when it happens?
Be honest!
Only approve what you can’t recover from. Like insurances: only insurance what you can’t pay for.
Remove friction by having more trust!
What do you think?
Power Platform Advisor
Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.
Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).
Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.
Services:
– Strategy and tactics advise
– Automating and integrating
A daily newsletter on automation and eliminating friction
FluentAssertions v8 is now paid software Free: Assert.True(result); $130 per developer: result.Should().BeTrue(); 😱 dotnet
Progressive Enhancement for JS is overrated. In today’s web, HTML + CSS + JS is a package deal. Almost every browser supports the trio, and let’s be real: users expect apps to work smoothly with JavaScript. 95%+ of users have JS enabled – why build for the exception?...
Alpine.js just clicked. 🎯 Its declarative syntax—attributes on HTML tags—is perfect for simple UI logic. Most of the time, I don’t even need to touch JavaScript. And when I do? I can write just a little bit, and it fits right in. What’s even better? The declarative...