Microsoft Flow

Creating a custom Microsoft Flow template gallery for your organization (part 2)

This flow internal template gallery was designed and built in partnership with Daniel Glenn, Office Apps & Services MVP. For more information about the template gallery solution we developed, check out Daniel’s blog post and his Microsoft Ignite 2018 session.

In my earlier post, I laid out a business case for creating an internal Microsoft Flow template gallery for your organization. The internal template gallery enables you to build and share custom Microsoft Flows within your Office 365 tenant. The gallery ensures company data and internal data connections in your flow templates are secure, while safely enabling your users to pool their collective knowledge and avoid re-work in building flows. You can also create a formal approval process for internal flow templates. The process ensures that flow templates are reviewed for accuracy and are appropriate for internal sharing.

But we don’t have to stop there. We can take this template gallery idea several steps farther by creating a Microsoft Flow Resource Community. The resource community can serve as a self-service gathering place for Microsoft Flow users in your organization, complete with links to training resources, Yammer discussion groups, your internal template gallery, etc. The resource community will:

  • Promote the use of Microsoft Flow by providing “getting started” materials for new users and a place for advanced users to share what they know
  • Support open dialogue and troubleshooting of flow issues
  • Prevent users from having to “recreate the wheel” by enabling easy re-use of flow templates
  • Provide a browsable interface for reviewing and downloading flow templates
  • Enable the submission and approval of flow templates for internal sharing
  • Drive engagement and adoption by providing a “community space” for Microsoft Flow

We recommend building your Microsoft Flow Resource Community on a SharePoint Online Communications site. You’ll want to customize the contents of your resource community, but here’s a list of suggestions to get you started:

  • Links to internal and external Microsoft Flow resources (e.g. 100-level introduction to flow, Microsoft’s flow guided learning site, the official Microsoft Flow team blog, and the Microsoft Flow Community).
  • Events calendar that highlights flow and other Office 365 learning opportunities
  • Microsoft Flow internal template gallery
  • Instructions on how to download flow templates from the gallery and leverage them to deploy new flows
  • Live display of Yammer conversations related to Microsoft Flow
  • Links to your Microsoft Flow governance policies
  • Information on where people can go to get advanced flow help

Most important–make the site relevant, engaging, and full of great flow content!

Now that we know what a Microsoft Flow Resource Community is, let’s take a look at a sample site.

The home page
We wanted a graphic, engaging home page for our Microsoft Flow Resource Community. The hero web part at the top of the page contains links to various flow learning resources. The remainder of the page includes our flow template catalog, a display of our Microsoft Flow Yammer group, and a list of upcoming Office 365 events. (Note: We elected to use the classic Yammer web part on our site because it enables full engagement. Users can like and comment on Yammer posts directly from the resource community without having to open Yammer in a new browser tab. For more information on the available Yammer web parts and the differencees between them, see my Yammer web part blog post.)

Flow_resource_community_01

Our flow template catalog is built using a series of News pages–one page for each flow template. News pages are stored in the Site Pages library, and the catalog is displayed on the site home page via the News web part. To help users quickly see which app(s) are included in the flow template, we added an app graphic to each template news page.

Let’s take a look at one of our template news pages in more detail. The banner across the top of the page displays the name of the flow template and the related app(s) the flow uses. Screen shots of the flow are displayed on the left, along with a clickable link to download the flow ZIP file template. A detailed description of the flow is provided on the right. The description pages for all flow templates include the same standard information–a description of how the flow works, a list of the required Office 365 or external application connections that the flow requires (e.g. a valid OneDrive account, a valid Box account, etc.), and a link to instructions on how to use the flow template ZIP file. A comments box at the bottom of the page enables users to comment on each of the templates.

Flow_resource_community_02

If you want to enable all Microsoft Flow users in your organization to submit workflow templates to your gallery, you may want to consider building out a review and approval process. Consider your must-have safety controls and review requirements as you build out this gatekeeping process. While governance is important, all governance policies and procedures should drive innate value.

We hope this Microsoft Flow Resource Community sparks your creativity. Best of luck in creating a site of your own!

Driving adoption of Microsoft Flow

Depositphotos_70209473_originalIn the land of Office 365, Microsoft Flow users are unique. While most of your users may use Outlook for email, OneDrive for file storage, and Microsoft Teams for intra-team collaboration, not all your users will create and leverage flows. Your approach to Microsoft Flow user adoption needs to account for this uniqueness. While you can launch broad Office 365 awareness campaigns, you will need to create a targeted adoption model just for Microsoft Flow.

Your user adoption campaign should focus on 4 key goals:

  1. Make flow relevant. Show your users how Microsoft Flow can help them meet their business goals. Making flow relevant to their daily work lives will drive home the why.
  2. Make flow achievable. Some innovators may start using Microsoft Flow based on word-of-mouth discussions or native curiosity about what the app can do. But the vast majority of your users will need help breaking through the conceptual barriers to using flow. They need an easy way to learn the basics, easy wins that can boost their confidence, and a method for getting peer or expert IT support as they start building more advanced workflows.
  3. Give your users a running start. Teach your users how to leverage Microsoft’s existing flow template gallery. And to drive stronger adoption and greater ROI, consider building out a series of company-specific flow templates that can be re-used internally.
  4. Make them shine. Provide your users with the educational materials and coaching they need to build flows that will make a difference and drive business value. Turning new flow users into flow superheroes will ensure continued adoption.

Planning for your flow user adoption campaign
To get started, you will need to clearly identify your target audience. I recommend creating formal personas for each of the key user groups you believe will leverage Microsoft Flow. You may have a business user, for example, that creates flows to help drive departmental process improvements. You may have a developer that creates flows as part of an agile engineering team. Identifying key types of flow users, documenting the reasons why they would leverage flow, and identifying their technology learning preferences will lay the groundwork for your custom user adoption campaign.

Once you identify your user personas, start building a target estimate for flow user volume. The estimate should project the rate at which users will start leveraging flow. If you have 1,000 Office 365 users, for example, you may target having 10% of your users adopt Microsoft Flow within the first 12 months. Your flow user adoption plans should account for driving this user growth, and monthly checks should be performed to measure your adoption efforts against your defined goals.

Now that you’ve identified your target adoption rate, it’s time to start building your flow user adoption campaign. It’s vital that you design your campaign to reflect and complement your organization’s culture. Look at programs that have succeeded or failed in your organization and unpack the key lessons learned. Determine what types of education and communication initiatives work well in your organization. If employees at your company don’t engage with or read news stories published on your company intranet, then publishing mass-market intranet articles about flow will not yield much success. If brown bags are popular, consider hosting targeted lunch and learns for each of your core Microsoft Flow user personas.

You also need to determine how to invest your valuable time and user adoption efforts. As I explain in Change by color: The secret of green dots, yellow dots and red dots, some of your users will readily accept change and be driven to adopt new technologies based on an intrinsic desire to learn and grow. Invest in these change adopters, but don’t overcommit your time. Target your efforts on the users that are slower to adapt but are still willing to change and learn new technologies.

Once you’ve defined your user personas and built specific user adoption campaign ideas that fit your corporate culture, you’re ready! Identify business needs and existing work processes that can be improved using Microsoft Flow. Leverage these opportunities as “starter projects” that will show of flow’s capabilities. Ensure you’re working alongside key influencers and innovators on your business teams for these starter projects. You want to engage with users that embrace technology and are quick to adopt. They’ll be willing to hear new ideas and, if they’re successful, will be able to evangelize flow’s capabilities. If you have resources that are already knowledgeable about Microsoft Flow (e.g. pilot testers or members of IT), introduce them to key business users and foster peer mentorship opportunities.

Most importantly, remember that flow user adoption isn’t a one-time project. In order for flow user adoption to become a reality, you need to treat it as an ongoing service. And yes, you’ll need to build, evolve, and drive your adoption program from now until the day you stop leveraging Microsoft Flow. Even the most successful adoption programs will die without dedicated attention and fresh ideas.

 

 

Creating a custom Microsoft Flow template gallery for your organization (part 1)

Microsoft Flow comes with a wide array of templates you can use and customize to build the workflow capabilities you need. The templates serve as both a quick-start guide and a learning tool. You can use the templates as-is or review the templates to see how others have built custom flows. You can share flow templates you create by submitting them to Microsoft’s template gallery. If Microsoft approves your flow, it will be made available to all flow users.

FlowResourceCenter_08

Microsoft Flow template gallery

But what if you want to share Microsoft Flow templates internally within your organization? Microsoft’s flow template gallery is open to the public, and doesn’t provide any safeguards for securing your internal company data or custom internal data connections. But since Microsoft Flow enables you to export and import workflows, you can build your own custom flow template gallery in SharePoint Online. You can use your gallery to:

  • Provide a browsable interface for reviewing and downloading flow templates
  • Enable the submission and approval of templates for internal sharing
  • Provide a community space where you users can access flow how-to videos and share learnings with others
  • Give your Office 365 users a jump-start for learning Microsoft Flow

In the coming weeks, I’ll be publishing a series of blog posts with recommendations on building an internal flow template gallery in SharePoint Online. I’ll also share ideas on driving adoption of Microsoft Flow. (Hint: Flow isn’t like Teams or email. Your flow users are unique, and your flow adoption plan needs to be targeted and specific as well.) I also recommend checking out Daniel Glenn’s Ignite 2018 session THR1111 – Creating a custom Microsoft Flow template gallery in SharePoint. The session provides background information on how an internal gallery can support flow usage. Thanks to Daniel for partnering with me on our concept and design for this internal flow template gallery.

See follow-up posts:

Welcoming the magic of Flow to OneDrive

In November 2017, Microsoft released its integration between Flow and OneDrive. Users can now create flows in OneDrive that will perform actions on OneDrive documents or folders. There are a wide variety of flows you can create, including:

  • Saving a copy of email attachments to a specified OneDrive folder
  • Routing OneDrive file(s) for approval
  • Sending OneDrive file(s) to other users
  • Sending links to OneDrive file(s)
  • Requesting feedback on OneDrive file(s)
  • Sending OneDrive file(s) to Microsoft Teams
  • Setting up alerts when new document(s) are uploaded
  • Searching for files in a given OneDrive folder
  • Copying OneDrive files
  • Converting OneDrive files to PDF
  • And more….

Because I present at multiple conferences/events per year, I wanted to test the capability of using Flow to convert my PowerPoint files to PDFs for easy sharing with conference attendees. I set up a flow in OneDrive to perform a PDF conversion on whichever files I select. I was able to use one of Microsoft’s standardized templates for the flow, with only a couple of minor tweaks.

Here are the steps to re-create this PDF conversion flow:

  1. Open OneDrive.
  2. Click on the Flow link in the OneDrive ribbon and select Create a flow.
    Flow_OneDrive_01
  3. When the window of flow templates appears, select the Convert selected file to PDF option.
    Flow_OneDrive_02If this is your first time using Flow, you’ll be asked to choose your country and click on the Get started button.
  4. You’ll be taken to a detail page that has information on the Convert selected file to PDF template. If this is your first time using Flow, you may be prompted to sign in and authenticate to OneDrive so the flow can be built. Simply click the Sign in button to log in. Once you’re logged in successfully, the Sign in button will be replaced with a Continue button. Click Continue to start working on your flow.
    Flow_OneDrive_03
  5. The template will populate, showing you all the preconfigured options for your flow. The flow is designed to save the selected file in PDF format and upload it to the root of your OneDrive folder structure. These default options are good, but I opted to make two changes to my flow:
    1. I clicked into the Flow name field and re-named my flow to PDF converter flow. This is the name that will show up in my menu of flows to run in OneDrive.
    2. I wanted all my converted PDF files to be stored in my OneDrive Presentations folder. To configure this option, I opened the Create file step and specified the creation folder path of /Presentations. (Note: If you choose to use a custom folder to store your PDFs, you must create the folder in OneDrive before you can specify the folder name in your flow.)
    3. Once these changes were made, I clicked on the Create flow option to create my new flow:
    4. Flow_OneDrive_04.png
  6. Once my flow is created, I’m taken to the complete screen. All I need to do is click Done to exit.
    Flow_OneDrive_05
  7. Now I’m taken to the overview page for my new flow. I can see that this flow is turned on and is set up to run on my OneDrive account. I also see a run history box. An audit record for each run of this flow will be recorded in the run history.
    Flow_OneDrive_06
  8. Now I’m ready to return to OneDrive and test my new flow. To do this, I navigated back to OneDrive, selected the file I wanted to convert to PDF, clicked on the Flow dropdown menu and selected my new PDF converter flow.
    Flow_OneDrive_07
  9. After waiting 5-10 seconds, I refreshed my page and there’s my new PDF!
    Flow_OneDrive_08

A few lessons I learned during the process of setting up this new flow:

  • Neither the free version of Flow nor the E1 tenant license supports PDF document conversions. While the free version of Flow and my E1 tenant could be used to create other flows, the PDF converter required at least an E3 Flow license.
  • The PDF conversion flow can’t be run against multiple files at once. I had to start the PDF converter flow for each file individually.
  • PDF conversion speeds are variable based on file size. A 51MB PowerPoint file took almost a minute to convert. Small PowerPoint files converted in under 8 seconds.

If you’d like more information on the integration between Flow and OneDrive, read the blog post announcement from the Flow team.