I work in the business of dealing with customer questions on Microsoft 365 all the time (disclosure), either directly or indirectly. This is part of a series of posts where I share them if they can be of help to others. Where I can of course and naturally, not just the questions but the answers too. All questions and answers strive to respect both sides sensitivities (parts will have been redacted and/or anonymised) and the main topic is covered in each post title.
This was not so much a question as a request to present to all the hackers participating in the company hackathon in a launch event. I put a few slides together, here they are in a pdf below. Below that, a few notes of elaboration on the slides that I think need it. This follows earlier advice I shared with the same customer on how to organise the hackathon, captured in this story: How to run a Hackathon for Microsoft Teams and Power Platform. And it also builds on this earlier thought rocket: Hackathons the MVP and lean startup.
I wanted to instil some lean startup, entrepreneurial thinking into the hackers minds. This is also a setup for some of the later slides. The main point being that you have to have an idea of what you want to build in the way of problem/s to solve or opportunity/ies to leverage and that by definition (being future focused), you are not going to be certain that you can achieve it. I wanted to juxtapose this with the need to start building and iterating fast and testing your work as you go and that this has to mapped against your vision and course correction will be required all along the way. Course correction will require either that you refine your vision or your solution.
The clear point here is that you should try and build complete solutions (as far as possible) at every stage of your build. It follows naturally from the previous slide too. I also made the point that they should not be myopic in their thinking and focus too much on the technology or “product”. For instance, building a wheel which on its own, is not really usable. Rather they should think about solving a transport problem and in the image example, a skateboard could be a great first version, perfectly usable in its own right. Hopefully you get the point.
While the hackers were mostly focused on building apps, automations, reports and the like with the Power Platform, I did want to bring Microsoft Teams into the picture as the platform through which they should consider publishing their work. I made two points really. One is that they could develop their solutions either in the respective standalone environment in Power Platform but they could also create solutions directly from within the Teams environment – more on that here: Create low-code custom apps for Microsoft Teams – Teams | Microsoft Docs. More importantly, that they should think about bringing their solutions into Teams to become collaborative apps – a concept explained really well here: Stay in the flow of work with new collaborative apps for Microsoft Teams – Microsoft 365 Blog.