Mike Fitzmaurice
VP - North America, WEBCON
Halifax, Canada
Mike Fitzmaurice, WEBCON's Chief Evangelist and VP - North America, is a recognized thought leader in workflow/business process automation, citizen development, and low-code/no-code solution platforms and strategies. He has spent over three decades on product, consulting, evangelism, engineering, and IT management. His decade at Microsoft included being the original technical product manager for SharePoint, having birthed, developed, and led developer evangelism on SharePoint through its first three releases. Other gigs included a decade at Nintex as Vice-President of Workflow and Product Technology and five years as Director of IT at the National Association of Broadcasters.
Topics
Which Tool is Right for Which Business Process and/or Automation Requirements
Power Automate is a great fit for many automation problems. But there's more than one kind of automation problem, and some business process solutions require more than just automation.
Some automation problems need transaction support. Others need to manage content. Some involve data harvesting. Or systems administration. Or data synchronization. Different use cases need different types of tools.
There's also a whole class of applications that focus on much more than automated activity, factoring in roles, assets, user interfaces, security, task logistics, strategy and tactics, and more. We'll talk about that, too.
This session is all about making sure you use a hammer to pound nails and a screwdriver to twist bolts; we'll mention some third-party offerings in addition to Microsoft-delivered tech, but we won't play favorites.
When to Use Which Kind of Automation, Business Process, Integration, or Workflow Tool
Power Automate is great for many automation problems, but no tool fits 100% of them. Even when it's the right choice, there are right and wrong ways to use it.
Some automation problems need transaction logic. Others involve routing content Some involve data harvesting and synchronization. Business process problems combine automation with assets, roles, goals, metrics, and more.
There are a lot of use cases, and they call out for different types of tools. We'll mention some third-party offerings in addition to Microsoft-delivered tech, but we won't play favorites.
When To Use What: Using The Automation Tool for The Right Task
Microsoft Flow is a great fit for many automation problems. But there's more than one kind of Flow. Some business problems that need transaction support. Others need to manage content Some involve data harvesting. Or systems administration. Or data synchronization. Different use cases need different types of tools. This session is all about making sure you use a hammer to pound nails and a screwdriver to twist bolts; we'll mention some third-party offerings in addition to Microsoft-delivered tech, but we won't play favorites.
Building Business Processes that Can & Will Evolve: Product-Neutral Principles Anyone Can Use
Far more than data management apps, workflow solutions need to factor in the need for frequent change. You should expect even the best-designed models and applications to be regularly modified -- and that's a good thing.
This has an impact on how to design processes, how to create forms and reports, how to connect to external data, and how to maintain internal data.
This session will talk about reasons why workflow solutions need to be modified so often, why you should embrace this, and strategies and tactics for addressing it. Its advice can be applied to Microsoft Power Automate (Flow), SharePoint Designer, WEBCON, FireStart, Nintex, K2, or most anything else.
Pro Tip: Don't Punish Your Users
When designing user experiences, from business forms to elaborate websites, the goal should be to reward users for using your app. Too many solutions behave the opposite way, making users work harder and figure out more than they should. This will show you a way to rethink a bad app and turn it into a good one, providing reusable principles along the way.
Workflow Best Practices: What to Use When, and How to Use It Best
Which problems are best solved with workflow? Which tools should you use when? How should you approach building those solution? Which designs hold up best? Practical advice for anyone approaching automation -- in SharePoint and beyond.
Which Tool is Right for Which Business Process and/or Automation Requirements
Power Automate is a great fit for many automation problems. But there's more than one kind of automation problem, and some business process solutions require more than just automation.
Some automation problems need transaction support. Others need to manage content. Some involve data harvesting. Or systems administration. Or data synchronization. Different use cases need different types of tools.
There's also a whole class of applications that focus on much more than automated activity, factoring in roles, assets, user interfaces, security, task logistics, strategy and tactics, and more. We'll talk about that, too.
This session is all about making sure you use a hammer to pound nails and a screwdriver to twist bolts; we'll mention some third-party offerings in addition to Microsoft-delivered tech, but we won't play favorites.
Stages and State Machines: The Best Way to Model and Manage Workflows
One feature that helps justify the cost of Power Platform Premium licensing is Business Process Flows; they're the Power Automate implementation of stage/state machine logic. SharePoint Designer 2013 supports it, as do offerings by ISVs like WEBCON and Nintex. This session will start by explaining how stage-based designs and processes work, move on to why they're often far better than classic sequential processes, and conclude with examples of how to build and run such solutions. It's the most useful workflow "secret" you can possibly learn.
Rethinking Citizen Development
Many of us have been promoting for several years now the idea of non-developers building applications themselves. It's time to take a look at how that has worked out, where it's worked well, where it's been a disaster, and which factors -- technical and organizational -- determined the difference.
Building Business Processes that Can & Will Evolve: Product-Neutral Principles Anyone Can Use
Far more than data management apps, workflow solutions need to factor in the need for frequent change. You should expect even the best-designed models and applications to be regularly modified -- and that's a good thing.
This has an impact on how to design processes, how to create forms and reports, how to connect to external data, and how to maintain internal data.
This session will talk about reasons why workflow solutions need to be modified so often, why you should embrace this, and strategies and tactics for addressing it. Its advice can be applied to Microsoft Power Automate (Flow), SharePoint Designer, WEBCON, FireStart, Nintex, K2, or most anything else.
File Sharing and Collaboration with OneDrive, SharePoint and Teams
OneDrive, SharePoint, and Teams provide a rich set of solutions for sharing files with people inside and outside your organization, and working together in real time. This session provides an insider's look at the sharing model for OneDrive and SharePoint, with explanations of all the external sharing options available and when to use them. Learn how we're making sharing easier for senders and recipients while providing even more ways for administrators to customize sharing to fit their organizations.
FLO101 - When To Use What: One Tool Does Not Fit All Use Cases
Microsoft Flow is a great fit for many automation problems. But there's more than one kind of Flow. Some business problems that need transaction support. Others need to manage content Some involve data harvesting. Or systems administration. Or data synchronization. Different use cases need different types of tools.
This session is all about making sure you use a hammer to pound nails and a screwdriver to twist bolts; we'll mention some third-party offerings in addition to Microsoft-delivered tech, but we won't play favorites.
FLO303 - Thinking Through Workflow Problems and Designing Superior Solutions
You can use Flow, SharePoint Designer, WEBCON BPS, FireStart, Nintex, or K2 -- but using them well requires more than mastering tools. Oddly enough, too many workflow solutions treat the process itself as an afterthought.
Data and forms are important, but when designing a process-based solution, the process should dictate what data you need and what your users need to see/do. It has a big impact on user experience, app integration, compliance, and more.
This session will present advice you can use anywhere, with any toolset.
Citizen Development: Different Tools, Different Rules
Citizen development doesn't just involve using low-code/no-code tools to build apps. It means a different type of user involvement, different life cycles, and different expectations for both results and work product. This session will compare and contrast "real" development with citizen development and show what works where -- and how they can work together.
Business Processes Evolve, So Be Prepared
Far more than data management apps, workflow solutions need to factor in the need for frequent change. You should expect even the best-designed models and applications to be regularly modified -- and that's a good thing.
This has an impact on how to design processes, how to create forms/reports/other assets, and how to connect to external data and maintain internal data.
This session will talk about reasons why workflow solutions need to be modified so often, why you should embrace this, and strategies for addressing it. It's advice that can be applied to Microsoft Flow, SharePoint Designer, WEBCON BPS, FireStart, Nintex, K2, or anything else.
Thinking Through Workflow Problems and Designing Superior Solutions
You can use Flow, SharePoint Designer, WEBCON BPS, FireStart, Nintex, or K2 -- but using them well requires more than mastering tools. Oddly enough, too many workflow solutions treat the process itself as an afterthought. Data and forms are important, but when designing a process-based solution, the process should dictate what data you need and what your users need to see/do. It has a big impact on user experience, app integration, compliance, and more. This session will present advice you can use anywhere, with any toolset.
Citizen Development: Inevitable, Ultimiately Desirable, and Perfect for SharePoint
Citizen development, love it or hate it, is everywhere. It's also known as solution-building, solution creation, low-code/no-code development, etc., but what does it really mean? Is it a job role, a tool set, a methodology? Do we define it by what it is -- or by what it is not? And what role is played by SharePoint, Office 365, and other platforms? Is it something "real" developer should care about? IT? You likely won't have the luxury of deciding whether or not to allow it -- it's already here. You can, however, decide how to make it work for you, what to encourage/discourage, and how manage it optimally. This talk is all about how to do it right -- and, of course, how to do it in SharePoint.
Professional Development, Low-Code/No-Code Development, and Citizen Development
What to Use Where, How to Use Them Together, and How It Changes Organizations
In Workflow Apps, Put The Process First
Data and User Interfaces are important, but when designing a process-based solution, it's the process that informs what data is needed and what users need to see/do. Data-centric and process-centric apps each have their places, but the rules are different, and this short session will spell them out.
365 EduCon DC 2021 Sessionize Event
Modern WorkPlace Summit Sessionize Event
Office 365 Saturday Redmond 2020 Sessionize Event
Office 365 Saturday San Diego 2020 Sessionize Event
SharePoint Fest Chicago 2019 Sessionize Event
SharePoint and Office365 Saturday Munich 2019 Sessionize Event
SharePoint Saturday Twin Cities Sessionize Event
SPS Los Angeles Sessionize Event
SharePoint Fest Seattle 2019 Sessionize Event
SharePoint Saturday London 2019 Sessionize Event
SharePoint Fest DC 2019 Sessionize Event
SharePoint Saturday Warsaw 2019 Sessionize Event
The North American Collaboration Summit 2019 Sessionize Event
SharePoint Saturday Bremen/North Germany 2019 Sessionize Event
SharePoint Saturday Vienna 2018 Sessionize Event
SharePoint Saturday Twin Cities Sessionize Event
Office 365 Saturday Redmond Sessionize Event
European Collaboration Summit 2018 Sessionize Event
SharePoint Unite Sessionize Event
European Collaboration Summit 2017 Sessionize Event
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top