This podcast by AgilePoint brings you fresh ideas from the trenches every week. It's not a step-by-step guide but a sneak peek into the minds of experts with field-tested ideas, templates, and frameworks they have used to implement digital transformation programs, for other enterprises. If you want to be sure you get practical and focused advice about enterprise digital transformation in under an hour, don't miss an episode.
Useful Resources mentioned in the Podcast
Concepts & Ideas
Tools & Resources
Apps
Key Takeaways
Hans Hantson Intro 00:00—05:03
Innovation Managers & Citizen Development 05:04—12:33
Misunderstanding about Low Code No Code 13:09—21:55
PMI Handbook and Customer Inspirations 22:55—37:04
Key Takeaways
Process Improvement & Matt Hubbard's Intro 00:00—06:06
Citizen Development 07:05—08:27
Matt's Citizen Development Journey 09:32—19:30
Citizen Development at Scale 21:37—34:18
Advice to Get Started with Citizen Development 35:08—42:17
Quotes
So I often preach, never automate a crappy process unless it's your goal to produce crap faster.As Benjamin Franklin said, Tell me and I forget, teach me and I remember, involve me and I learn.It's important to think through processes before flipping the automation switch. Citizen Developers are, they are problem solvers. If you are one who is okay with the way things are today, you like coming in, doing your job, checking the box, and going home, then I would probably say Citizen Development is not for you.I thought, why can't we do that with business applications? Why can't we have a platform that already exists, like the home console for Atari?Process problems and system problems are kind of ubiquitous. They kind of exist at every company. And, this app-building platform, which would later be categorized as low code, no code was back in play. And to make a long story short, I started learning the platform and building my own apps. I'm not a coder; I'm a process person. I think one of the reasons why it didn't scale for me is that I didn't approach Citizen Development in partnership with IT and executive leaders. I have a mantra that I followed when I ran my consulting business and I adhere to it today, and it's called Think Big, Start Small Scale Fast.
Key Takeaways
[0:00] Microsoft Power Platform’s governance is all about putting the guardrails around the low code platform so that the citizens can keep on developing apps to solve their own problems, deliver a good user experience, and allow them to innovate without locking their activities with IT policies.
[7:40] Low-code products like Power Platform aim to fuel a bottom-up innovation.
[8:06] There’s a lot of hype around low-code no-code platforms but a lot of companies don’t understand how they can use these platforms in their environment.
[11:50] Jukka and his team of consultants often find individuals or teams using Microsoft Power Platform to build solutions, especially those who were not able to get them built through their IT departments. These are not necessarily the most beautiful apps from a UI or architecture perspective, but very effective from the business results perspective.
[13:20] You need to find those heroes within the organization who already understand that there’s a business need for low-code platforms. These are the folks who are frustrated by the lack of official systems or how long it takes to build them.
[14:40] Power Platform is better than just using the Power Apps because through the platform you can enforce policies and processes to govern several types of solutions and apps.
[16:15] What people generally misunderstand about Power Platform is its commercial plan and positioning of it because Microsoft has bundled Power Apps, Power Automate, and Flow into Office 365 from day one.
[19:27] The big question is whether Power Platform will also be for vendors to build their own products on top of it. Until now what Microsoft has mostly celebrated is Citizen Developers. Jukka and his team have also built their own product on top of the Power Platform, and they call it the ‘Sustainability Action Pack’.
[27:25] Microsoft Power Platform charges users based on license-per-user so you have to assess which use cases it is most suitable for. It might be fit for some use cases but not the right toolkit for consumer-facing apps and scenarios.
[28:20] Power Platform’s future direction can be assessed by seeing how it evolved during the past four years. In the first two years, the focus was still on catering to app makers’ needs, integrating capabilities of Dynamics CRM and Dataverse. During the past two years, the focus was still a lot on admin tools and governance capabilities of the platform.
[32:00] The way we frame Power Platform governance to our customers is that you need policies, controls, and processes for people who are not pro-developers, do not do it for a living, and who don’t have a formal education background in software development. Allow them to use pieces from the cloud in a sensible way.
[34:00] Internal evangelism is important to make LCNC initiatives successful.
[45:00] CRM consultants have done a lot of good work in evangelizing CRMs in organizations, so that type of effort is needed to make Low Code No Code more acceptable.
Quotes
“The way we frame Power Platform’s governance to our customers is that it's all about putting the guardrails all-around low code platforms”.
“We are really more focused on helping the organizations themselves take ownership of their tools and build new applications for scenarios that previously haven't had any apps or automation in place”.
“From an IT perspective, the power platform is unique in the sense that many organizations already have it, even though they haven't acquired it. And that's the result of the Microsoft strategy to bundle it with their Office and Dynamics tools”.
“Users of Low Code tools are people who have usually been frustrated by the lack of official systems or how long it takes to get something budgeted and implemented”.
Listen to AgilePoint Podcasts on https://www.agilepoint.com/podcast
Note: Based on the title of this podcast, if you want to directly listen to Ian Duncan's take on 'Why Transformations fail?' and a meta-framework he uses to approach transformation program management, head over to this timestamp [00:26— 00:51].
If you prefer to understand the nuances involved in large-scale transformation programs, it's best to listen to the whole episode.
Episode Summary
List of Resources Discussed in the Podcast
List of topics/themes discussed in the episode
List of topics/themes discussed in the episode