Category Archives: My 2 Cents

M365 Twin Cities Logo

M365 Twin Cities – Conference Event

M365 Twin Cities is the evolution of SharePoint Saturday Twin Cities and is a Community Days event. As a part of Community Days, we’re also aligned with MGCI – Microsoft’s Global Community Initiative.

We cover topics from M365, Copilot, Power Platform and anything related or adjacent to M365 like Azure, governance, security, and a lot more. Our audience also falls across many personas: Users, decision makers, power users, makers, developers, administrators, and others.

As we’re currently preparing for our 2026 event, let’s recap our 2025 event a bit.

2025 Event By the Numbers

Our 2025 event was on Friday September 19, 2025. We had 705 registrations prior to the event with a number of folks that registered at the event. All in all, we had about 380 folks on site (that’s a pretty normal ratio against registrations). The attendee numbers were a good trend from 2024 where we had about 250 folks – steadily growing post-pandemic.

Registration – Ready to go!

The ‘vibe’ was overwhelmingly positive. The higher attendance was immediately obvious and contributed to the higher energy in the room from both attendees and sponsors. As our community usually does, they hit up the sponsors early – even before our opening info session. The coffee and donuts may have helped as well.

We had 31 sessions with 33 speakers across 8 rooms – with the largest session attendance topping out around 110 people! Learning was had by all.

Sponsorships post-pandemic were, and still are, a challenge. The market has changed, the economy has changed, and how sponsors engage with customers has changed. Where we had a little budgetary buffer in the past (pre-pandemic), events are tough to fully fund. We’re hopeful that rising attendee numbers will help bring sponsors back. Our 2025 event had 8 wonderful and fully engaged sponsors.

Locally, we’ve got a really strong Microsoft community – a healthy SharePoint history and M365 adoption across businesses, government, and other organizations. While this is mostly a good thing, it also drives a bit of competition with other groups and events within our community. While this is great for attendees, it’s tough on sponsors and event producers. There’s only so much funding to go around and tight budgets can impact community-driven (and funded) events like ours.

Historically we’ve had 1-2 events a year with 2 events most years. Coming back post-pandemic we’ve tended towards a single event – *and* moved to Fridays – in an effort to make sponsorship funding more reasonable for our supporting vendors.

Next up – Fall Event

Our 2026 event will be held on Friday September 18, 2026. Registration is open. We’re working on session selection and aim to have the schedule up in a few weeks.

Companion apps screenshots

M365 Companion Apps – Coming to Windows 11 Machines Near You

Or not… But it’s on by default (of course).

If you follow the Message Center – administrative updates for your M365 tenant but available to anyone really – you may have seen a recent announcement about “NEW Microsoft 365 companion apps…”. There’s a lot to unpack here. First detail that caught my attention however was that they are intending to *automatically* install software on your PC – not a shock, but also something I’m not generally a fan of without more information and prior planning – hence this heads-up for folks.

The Roadmap ID for this change isn’t useful at all. But the Message Center post is well done with lots of details, references, and highlights including how to opt-out of automatic installation (without having to use PowerShell!).

So, what’s Microsoft up to this time? Why the push of client-side apps? What aren’t they getting with their cloud-based solutions? Again, there’s lots to unpack but the Message Center highlights give a good overview.

What’s Installed

There are three apps installed: People, File Search, and Calendar. These can be installed manually – as a set, not individually – via the Microsoft 365 companion app installer.

People and File Search are unique enough to find and launch easily. Be aware however that the new Calendar companion app can be confused with the existing (New Outlook) Calendar app.

The old app/icon:

Old / Outlook Calendar

The new companion app/icon:

New Calendar Companion

Functionality of the apps will vary depending on other licensing and configuration, including Copilot in your environment and tenant. An overview of the companion apps can be found here: Microsoft 365 companions apps overview – Microsoft 365 Apps | Microsoft Learn

More to come…

References

Notes / News / Thoughts

Learning – Keep at it

This past weekend I attended a white coat ceremony for the first time. This is a (newer) rite of passage for incoming medical students as they begin their journey to becoming medical professionals. In preparation for the ceremony, each of the classes (degrees/programs) crafted their own oath and each of the three we heard that afternoon included a commitment to continued learning.

This commitment to learning shouldn’t come as a surprise, especially in the medical fields. Technology changes. Our collective understanding of health, medicine, and the human body grows. We expect the highest quality, experience, and knowledge from our health care workers. These professionals need to set time aside for ongoing learning. And they do.

What about those of us in the technology and/or business world?

For starters, most of us aren’t taking oaths for our jobs, but I’m still a fan of making ongoing learning a good practice. I don’t have the stats to back it up for this quick article, but I’m pretty confident learning is good for our mental health. I know keeping up with the latest technology is a requirement for many of us in the tech world if we are going to have effective knowledge of technology capabilities and best practices. With so much change happening so fast it’s hard to keep up or even stay ahead of our users and customers sometimes. AI is just the latest hot topic but change in our world is rapid and not slowing any time soon.

As consumers we experiment (or ‘play’ depending on your perspective) with the tools, we read docs and blogs, we listen to podcasts, and attend training and conferences. Sometimes we do it with management support (funding and time), though often on our own dime and time.

What’s your approach?

  • Do you listen to podcasts on your way to work?
  • Do you read an article a day or have daily micro-learning approaches?
  • Do you save up your time and do deeper dive research that might last longer periods every so often?
  • Regular training or conferences via your employer? Check out Community Days for local opportunities!

What works? What doesn’t?

Are you only consuming? Or are you sharing your knowledge with others as well?

Speaker and session selection for an M365 community event.

M365 Twin Cities – Session Selection

Uffda. This is the recurring (now annual) “picking sessions and speakers for an event is hard” post.

How it starts

  • 32 session slots available (8 rooms, 4 time slots)
    • Of these, we reserve 4 for potential sponsored sessions. These may be freed up for other content as we get closer to the event if we don’t find sponsors to fill them.
    • This leaves 28 session slots for community speaker sessions
    • NOTE: We’ve had more rooms in the past, but this tends to dilute attendance per session. Fewer rooms tend to raise the number of attendees per session which is nice for presenters. Like anything this is a variable we tweak and adjust as we don’t want rooms too crowded either.
  • 109 sessions submitted from 53 speakers
    • Yes – a LOT of Copilot/AI topics this time around. We’ll have plenty but there’s still lots of other relevant topics to talk about.
    • We had a notable jump in new speakers submitting – mostly out of town folks that we don’t know personally. I’m curious what drove that… We didn’t change anything that I’m aware of when it comes to Call for Speakers or communications. Interesting.
    • As with every event, we also had a number of “regulars” – friends and colleagues – that didn’t submit, which is disappointing. They each have their reasons. When it’s our fault with scheduling it hurts a bit, but we do our best – scheduling is also tough. It’s a bummer to miss opportunities to host and hang out with friends we’ve made in the community.

Our community is blessed with so many folks full of ideas, with wide varieties of experiences, and with the willingness and skills to share their knowledge with others.

Now, expectation setting… We never get this 100% correct for everyone. We guess who’s going to attend and what they want to hear. We base our decisions on previous events, on what we know about the technology, the topics, the speakers, past attendees, and all sorts of input. But we do our best to balance what we can.

Our panel consists of members of the leadership team. Your event and approach may vary. I’m sure there are other variations and ways to do this – maybe put together a content committee or something along those lines. We tend towards simplicity, so here we are.

Priorities, Variables, and Factors… How it comes together

There are a bunch of things we work towards balancing. We want to invite out-of-town speakers, but we like to favor local folks where we can as well. We want to give new speakers an opportunity to speak while also providing known quality speakers for attendees. Because of these priorities we don’t use the blind selection method (looking at titles and abstracts while hiding speaker names).

We leverage our event tool Sessionize where and how we can, sometimes using their selection/rating system and process, sometimes we tweak the methods. The tool does a wonderful job of collecting submissions and later notifying folks once decisions are made.

When it comes to topics, we try to find a variety of timely and relevant topics that apply to our attendee base. We’ll compare similar looking sessions. We’ll look for sessions that appeal to different roles in the M365 world, different products, etc.

Once we get the number of prospect sessions down to around the number we need, we switch gears and start looking at how those sessions fit into slots in the schedule. If we have too few or too many sessions around a topic or what might turn into a topic “track” then we start to massage the schedule to work as well as we can.

Our event doesn’t usually have a keynote. We’ve got a room for it now (we didn’t for a number of years) but attendees seem to prefer filling the time with as many sessions as possible. Better to have 8 topics to choose from for one of the time slots rather than just one and hope it appeals to most.

Finally, we slot the sessions and review the schedule for topic conflicts, overlaps, if speakers have more than one session (not many) they aren’t scheduled at the same time, etc.

Setting the schedule

We whittled the list down to 29 sessions (1 sponsor and 28 community sessions) with a number of backup sessions from the queue of speakers.

We have 33 speakers – a few sessions include more than one presenter. This means we have to turn down 20 folks. This is one of the hardest parts of the process. So many folks that took some of their valuable time to create sessions, write abstracts, and come up with titles. We don’t have room for them all to present, but we are thankful for them and hope they submit again.

Thoughts…

The concept of a content panel is interesting. It might be something to look at if attendee numbers continue to rise. We could also do some more polling of attendees to see what topics folks are interested to either verify our assumptions or give us more data to work with.

We get a step closer to the event

Visualize the comparison or battle between Microsoft's Power Platform and Pro-dev coded customization

Power Apps … *One* Option for Extending M365

This note is in response to Andrew Connell and Julie Turner’s YouTube video – “Ep. 009 | Microsoft 365 Extensibility: Power Platform isn’t the Only Option” – on their “Code. Deploy. Go Live.” YouTube channel.

The premise of their episode title and some of the take-aways that struck Andrew and Julie were:

  • “Power Platform is still king” – Julie’s observation while working the Ask the Experts table/panel and seeing the line – the demand – for Power Platform Q&A.
  • “The number of people that think that the way to build something custom on M365 – that your only option is Power Platform.” – Andrew’s observation after Seattle’s TechCon event.

I don’t necessarily disagree with these observations. Many folks that have dug into the Power Platform are invested… Power Apps and Power Automate have become their “hammer”, their tools of choice, their platform of preference and bias – both the community and marketing Microsoft has built around these tools does little to discourage that thinking.

Awareness

I don’t know if folks aren’t aware of other methods to customize M365, or if they simply aren’t driven to find or investigate other options. For many of these folks – folks in the Power Platform’s target audience – “development”, “pro-code”, etc. is a no-go. Many are business users that have little interest in becoming developers and shy away from conversations about actual coding.

As for me, while I focus on a range between out-of-box capabilities for power users of M365 through Power Apps makers, I try to include the full range of options available for folks in the conversation: from out of box capabilities, to tools like Power Platform that extend traditional platform capabilities, to pro-dev customizations. 3rd party products also figure in the mix and also change at a rate challenging to keep up with.

Power Platform is accessible

I’m not sure “accessible” is the right word… but for many M365 users the step up to Power Apps and Power Automate is a lot more approachable, achievable, reachable, and viable than stepping into the “pro-dev” development world. Mostly from a skills perspective. They can start experimenting with *some* Power Apps and Flows with very little effort and see results. Now, I understand that getting bigger results with Power Platform requires an investment of time and effort to do more advanced things. If someone were to compare efforts at becoming a high-level Power App maker with the effort to become an effective pro-developer resource… I’m not sure what that might look like. I am confident that most Power Apps folks would still choose Power Apps. Digging into the reasons for that would be interesting…

For a lot of folks, there’s a bit of disillusionment with IT and development. Developers are almost always overworked and have huge backlogs of work (new or maintenance) to keep them busy – making new requests hard to deliver on a timely basis. With that, lots of folks see opportunity with Power Apps as a way to get what they need from a business standpoint more quickly and easily.

Yes, those of us on the IT side know choosing that path comes with a price. But folks trying to get their jobs done will still do it and deal with the “other stuff” later. Often with the blessing of their (non-IT) managers.

Some organizations don’t have developers available in-house, so they need to engage with consultants – which cost money. These (usually) small to medium (“SMB”) organizations often resort to seeing how much they can get done with the tools and licensing they have available – which leads them to the Power Platform.

“Not Enterprise-Ready”

Most of the folks I work with are at the intro-level of Power Apps, where I’m making folks aware of what’s available within existing M365 licensing. While I’ve seen some larger implementations, I don’t (IMO) have enough experience there to say where the Power Platform may falter in enterprise-level implementations – specifically when it comes to the limitations of the platforms.

What I do know is that there is plenty of room for error in governance – both in planning and implementation. Most every pro-dev shop will enforce some level of application lifecycle management – or “ALM”. In short, this means they develop in an environment separate from the production data and functionality. While there are ways to implement ALM features with the Power Platform, it would be interesting to see stats on how many orgs that use Power Apps and flows are implementing ALM. Without ALM, they’re introducing risk to their environments. Risk to data. Risk to processes that can grow into business-critical levels. And more.

There are more Power Platform for M365 is “not ready” topics, but ALM is one of them.
I’d quickly add data to that list… where you choose to manage your data is important as solutions grow. Microsoft Lists and SharePoint Lists (the same thing) are wonderful tools for business users but have limitations and cede to Dataverse or SQL as they need to scale over time.

Final Thoughts… for now

*Some* of the perceptions above are biased by the conference’s target audience. I think we’ve been seeing fewer Developer attendees and more Power Platform folks.

Power Apps have their place in the maker/development/customization space. What role it plays, where triggers exist for review, migration, or other will vary from organization to organization. In an ideal world Power Platform tools are introduced to an environment in partnership with Pro-devs. ALM for Power Apps and flows are modeled on Pro-dev processes, and more.

I think Power Apps are a great way to extend List functionality – both with forms and data presentation.

I think it’d be great to see some Pro-Dev comparisons to each of the tools in the Power Platform space. Come up with some common scenarios where Power Apps, Flows, BI or other are implemented and discuss the efforts and capabilities of either approach…

It’s also important to get the “there are multiple approaches to customizations” conversation to decision makers – often the folks NOT at conferences. (generalization, not the rule…)

There are a lot of threads here that could be pulled… Lots to talk about. And lots of “it depends”. 🙂

… and we haven’t even touched how/where the D365 community differs from the M365 community and Power Platform’s piece of that conversation…

Features Lost in Complexity

“Complex and feature-rich tools…”

It’s a phrase I saw in a LinkedIn article not long ago that resonated with me as a concise way to convey two connected issues that we see users and organizations facing with enterprise software these days.

  • Product complexity – Leads to users not finding functionality they want intuitively in the interface.
  • Knowledge gaps – The larger the feature portfolio, the tougher it is for users to master the skills needed for their role or specific activities.

Now, complex and feature-rich tools are a good thing, right? They’re filled with so much promise. As new features are added and software grows, at some point these products can get more difficult for users to use – and more challenging to meet those ROI expectations. Not to mention the added twist we have now with cloud-based applications and the speed at which they change. It’s a moving target to get up to speed and stay up to date with features and our ability to leverage them.

While the article linked above talked about both business value and usage with HubSpot, the issues absolutely apply to Microsoft’s M365, Power Platform, and other enterprise platforms like Workday, ServiceNow, etc. as well. In-house custom applications aren’t immune either. In fact, custom solutions might be more challenged because they don’t have a level of support, documentation, or training that commercial products (should) have.

To make the problem worse, the biggest group of users are typically business users whose main priority isn’t learning software but is actually running the business.

“Does the product do this?”

The problems listed above are obviously related. As features are added, removed, or changed – training materials and resources need to keep up and users need time to consume them. But the changes keep coming, so it’s a never-ending effort. You end up with users at all levels and roles not aware of capabilities that could be impactful for them.

How do you address a large and complex set of features?
Maintain, or subscribe to, a definitive list of platform features, activities, skills, and capabilities. Sounds like it should be easy, but it’s usually not. Between the size and complexity of platforms these days and the rate of change, it’s difficult for folks to know what’s available, what’s not, what’s changing, etc.

How do you address knowledge gaps? How do users know what they don’t know?

  • Use assessments – *not* exams – to figure out where the gaps are. It’s not a pass/fail situation. It’s a non-punitive metric of what you have awareness of and what you don’t so you can put focus on the gaps when and if you need to.
  • Provide resources, training, champions, examples, and all the traditional materials for users to skill up when, where, and how they prefer to learn.

So, we do our best. If we have a platform team (or whatever it’s called in your organization) they can be responsible – as their job – for knowing the tool inside and out and understanding how the organization leverages the tool. They either create or work with a training department to create or source training and reference material. We utilize change management policies to deliver timely communication about changes coming, and the people/roles that are affected.

If you don’t have a platform team, there might be an IT generalist on the tech side or user “champions” on the business side that do their best to keep up with features and capabilities.

Prevention – Governance

Training, resources, change management… you name it. Get ahead of knowledge gaps by preparing materials and training sessions before introducing tools – when you can. But there’s still work to do after deployment.

Build and maintain training and other resources so you can leverage them throughout the lifecycle of the product or application. Maintaining resources is key for new users to an organization and folks that skill-up over time.

No plan, implementation, or organization is perfect though. There will always be gaps. There will always be new folks coming to the organization or to new roles and positions. The best we can do is set the environment and systems up as best we can with the staff, tools, and funding we have available.

3rd party tools and services might also be part of the mix. That list of features, skills, etc. mentioned above? Let someone else manage the definitive list. Focus your organization on the training materials needed for your situation. There are also tools like VisualSP that enable in-app, just in time learning for users. There are options. Find what works for your users.

Artificial Intelligence

AI is certainly going to help with issues like this as well. As product owners add AI chat interfaces, users will have more ways to search or ask for what they are looking for and have better results than previous “help” interfaces were able to support.

Set users up for success

This is the same message product owners, consultants, trainers, etc. have been preaching for years. Establish a location for users (not just “end users” but all roles) can come to find the info they need within your org. It might be called a “Center of Excellence”. It might be something you build, or a collection of tools, services, etc. you cobble together. You can start with common community-built knowledge, links, etc. and then curate or build organizational-specific knowledge, experiences, learning links, and more.

Finally, build momentum. With more folks using the software and platforms successfully, there will be more opportunities to share what they’re doing and how they’re doing it. Raise that collective awareness and skill level.

The Death of Community on Twitter / X

It seems we’ve hit the tipping point where the Twitter / X facet of the M365 / Power Platform / Microsoft community is effectively dead.

It’s not a loss that’s likely to be celebrated by a mock funeral at a Microsoft conference… (see InfoPath, etc.)

Many will applaud the shift – for whatever personal, political, or other reason they may have. Personally, I’m bummed – mostly at the loss of interaction, touch points, and availability of connecting with folks. I don’t think there’s been a better platform for *anyone* to connect with anyone and I don’t know of any other platform that’s doing it as well or better than Twitter did.

It was free. It was simple. For the most part if someone was on the platform, you could reach them. And in our community, many/most of us would respond when someone pinged us. It was a great tool that augmented conference engagement. If you attended, you could connect with speakers. If you weren’t attending a particular conference, you could “ride along” with the happenings by watching the feed. It was great for generating momentum and getting feedback without waiting for the follow-up posts.

Sarah, Antonio, and Mike recently touched on this as a part of their most recent M365 Voice podcast – Episode 127 – How to engage with M365 Community Members. I suppose this post is somewhat of a response to their conversation…

A considerable part of the audience, influencer, and community within the Microsoft technical community rejected the platform as a way to reject Musk and the combined “big tech” group behind social platforms. But it’s also not the only reason. Times are changing.

Content Overload

As consumers of content and media, we’re faced with an increasingly overwhelming amount of information, signals, notifications – being shoved down our throats – all the time – fighting for our attention. As noted by a few comments in the podcast mentioned above, many platforms are trying hard to push notifications – even fun ones like Bird Buddy (non-technical aside… 🙂 ) But we only have so much bandwidth, time, and attention.

There’s already been considerable pushback on overload and it’s likely to continue – which is good. Less “noise” is better for our mental health, our family time, our focus time, and more…

We’ll likely see more curation of content brought to us via AI solutions, agents, or whatever we need to narrow the stream and get the content we need while filtering out what we don’t.

Our community, however, has conflicting forces. On one hand we want to manage the noise and limit inputs, while on the other hand we have consistently increasing complexity. What used to be “just” SharePoint, is now a full suite of M365 applications, integrations, capabilities, and functionality that’s grown in both scope and depth.

A recent LinkedIn post by Ali Schwanke called out how “complex and feature-rich tools” challenges us with keeping up our skills and awareness. While her article referred to HubSpot, the issue absolutely applies in the M365 community as well.

What’s Next?

Where are you connecting with community? Do you feel a need to connect? Can you find the information you’re looking for with the platforms we have available?

For now, Microsoft and its leadership are still posting to X. They’ll continue to post on channels as long as it’s useful to reach their audiences. As the audience, we’ll keep trying to find balance between platforms and finding the information we need to best do our jobs and serve the community.

References / Links

Microsoft 365 Voice

Tech Conferences – Also for End Users

Maybe it’s me, but it seems that there aren’t enough end users at technical conferences. There are a variety of tech events out there and some of them are absolutely deeper dives for technical professionals. But there are more – either professionally produced or community-run – that include content for everyone.

Now, I could have said “training” instead of “conferences”, but training is more obvious (everyone needs it, including end users) and often covered by training departments within larger organizations. The conferences part here is also important because it involves networking with peers – usually outside of the organization. People with different perspectives and company cultures that can bring new ideas and approaches to common issues. Conferences are also great opportunities to interact with SMEs – either community contributors or the folks building the products.

Obviously, you can’t stop work and send everyone. But you can often send more than we’re currently seeing – especially free local events. These events aren’t just for IT. Ultimately, having end users in attendance can also help IT by bringing a business perspective to product features. And yes, these product feature conversations do still need to be tempered by IT realities: cost, time, risk, and many more…

We’ve always had end users at conferences, but never enough when you consider where and how the impact on business occurs and just how many users there are out there. The impact they make isn’t isolated though. It requires partnerships within each org. Users aren’t going to be successful if the platform isn’t deployed or configured correctly (IT Pros). Users aren’t going to be successful if platform owners don’t make connections between tech and business priorities, train users, and keep them up to speed.

Engaging technology to further the business requires awareness, skills, and a bit of balance between a number of teams. The benefits can be awesome.

End users are challenged by awareness, instruction, divided priorities, and limited time. We can group these a bit. Priorities and time go together as there’s often not enough time (this continues to get worse as organizations keep trying to get lean…) and business, not tools, are (and should be) the priority. Learning tools is secondary even if the end result makes the business more efficient.

Awareness and instruction go together with the awareness part often overlooked (also another topic…). Users need to get a grasp of what tools or capabilities are available (awareness) and then learn how to use them (instruction) when they’re relevant. In an ideal situation someone like a platform team or a customer success team may cover awareness in terms of what features are available and where they fit – translating between the tool and business needs. In many cases, however, IT can be a blocker of sorts… not letting users know features are available, or even disabling them.

Disabling features can very well be for legit reasons (security, conflicts with capability offered by other products, etc.). In some cases, they might not enable features until they’ve been tested and validated, IT trains up on them, or training materials are created. And again, we run into crunch time with IT not having enough time to dig in. If end users learn themselves about features, they can inquire about them with IT and help determine when it might be a business priority to deploy features and capabilities. It’s for each organization to find the balance that works for them between business needs, IT capabilities, and prioritizing them.

More than ever before (at least that I’ve seen) the makers of apps, tools, and services are reaching out directly to end users instead of relying on IT as an intermediary. They’re both building tools that appeal to end users and marketing directly to them. Microsoft Lists, for example, has been around for over 20 years (SharePoint, then Microsoft Lists) and is aimed at end users to manage information with structure. More recently the Microsoft Power Platform targeted all users with Power Automate and Power Apps – though I’d argue Power Apps is very much NOT for all users… but that’s another post. Currently, we’re in the midst of AI and Copilot rollouts that will have impact on everyone.

Summary

The more end users we can get at conferences, in training, and engaging within technical communities, the better. They can gain awareness to features and capabilities to understand where and when they might be useful in their business needs. They’ll know when to ask IT to turn a feature on they might not have access to initially. They can build personal networks and provide valuable feedback to product owners.

So, especially when it comes to local and free (or for marginal costs…) events, make the time when you are able to enable your employees and your teams to join the conversation! It’s good for mental health to step away from the grind every so often too. 🙂

Context and Perspective

My opinion and experience here is biased on several accounts:

  • I’m an event producer. Just small, local, community-run events, but still. I’m interested in getting folks to events both because I want events to be successful and because I want folks to have the opportunity to learn, to skill up, to become more effective with the tools they use (that’s why we put them on after all…).
  • I’m also involved with a group that promotes community events and encourages folks to produce them.
  • The tech spaces I work in (Microsoft M365, SharePoint, Lists, Teams, Power Apps, etc.) have historically been near the “edge” of where tech professionals, power users, and end users come together.
  • I speak at a variety of events – both community-run and larger commercial events.

References

  • M365 Twin Cities – Next one on Sept. 6, 2024 – The event I put on with a team of awesome folks
  • MGCI (Microsoft Global Community Initiative) – The organization I am associated with as a Regional Leader to
  • Community Days – Community-run events (Primarily. Others are listed as well) associated with MGCI’s efforts..
  • TechCon 365 – A larger professionally run event that typically produces 3 or so events per year across the US. A week-long event with workshops, keynotes, and sessions.
    If you’re interested in these, let me know as I often have discount codes available.
white printer paper

Delivering More Usable Power Apps

When folks start digging in with Power Apps (at least in my experience) they want to accomplish something business-related – trying to add functionality that was missing in their daily activity, their processes, their interactions with others, etc. Power Apps is great at that.

What early Power Apps makers (non-IT) don’t usually consider at first is branding, design, or accessibility. They build something that makes sense for them alone. The scope is one person or one team – which is completely fine – rather than a wider organizational view. For many projects that might be the end of it: “Boom, it works. Process improved”.

In some cases, those relatively small, “home-grown”, simple solutions gain a broader adoption (it gets more popular than originally intended…) – which can bring with it additional considerations… One of those “now more important” topics is UX/design.

As the size and capabilities of an organization increase, app makers often have more policies to follow and resources available. Branding standards and corporate color templates seem to be the first elements that get added. Designers are part the mix. As more resources become available within the org, there can be a variety of UX/design roles that include researchers, designers, and more. These folks can bring creativity and experience to the table that notably improve the look, feel, and functionality of apps.

If they are available in your organization, learn what resources are available and when to get these folks involved.

Investments in design and UX can potentially yield solutions with higher usability and user adoption rates. The same usability goals and techniques that apply to Power Apps also work with other apps and interfaces – this includes custom development as well as dashboards and cards in Teams and Power BI…

In an organization with established development ecosystem, processes and standards are likely being leveraged. Folks know what teams and resources are available. The quickly growing non-IT Power Platform maker population however might not be aware of these resources if they’re not looped-in with the established development org.
As a Power Apps enabled organization, strive to:

  • Learn the differences between the roles: UX, UI, designers (and others)
  • Understand the value UX folks bring to app development
  • Learn when to engage, how to best engage, and what to expect when engaging UX folks

With the popularity of Microsoft’s Power Platform and Power Apps, we’ve added lots of new folks to the maker community. These makers have new (or new to them) tools that enable them to build impactful business solutions but usually don’t have experience satisfying user experience needs of their users. The more you can integrate the UX expertise that’s available out there, the better the organization will be served by these dynamic app-generating efforts.

Note: This quick post was intended to make PA folks aware of UX resources… It’s a far cry from digging in to all the details, benefits, nuances, etc. that you’ll run into if you have the opportunity to work with that crowd. There can be a lot, but there’s also a lot of potential benefit for your users and more. Let me know what your experience is!

References:

More Coming… (Getting input from UX folks…)

Hey UX experts, let me know what other references and links I should add here!

  • What are some good resources for understanding the different roles?
  • What are good resources for understanding why, when and how to effectively engage the different roles?
  • Are there research articles that support effectiveness of UX when applied to the dev process?