We believe in being where the users already are. It’s an easy idea to grasp, but it’s not easy in practice.
It’s still the right thing to do.
If someone’s solution requires users to bookmark yet another website or add yet another app to their phones/tablets, it means someone opted to put the burden of work on the users. That rarely works.
People already share information with teammates and colleagues using services like Teams, Slack, Chatter, Yammer and LinkedIn. In fact, they’re already sick of having too many collaboration workspace technologies to choose from — and the result is that none of them are getting adopted to the degree their champions hoped.
They already interact with other people and companies via email, SMS texts, chatbots and voice assistants. They create documents in Office or G Suite. Heck, they already view, edit, and create information using forms native to Salesforce, native to SharePoint lists, custom web pages, or PDF forms.
And when it comes to work queues, they have email inboxes, Outlook tasks, Trello cards, Project tasks and more.
How about we not give them yet another place to visit and monitor?
Workflow’s Rightful Role
It’s our job to connect to those services and orchestrate activity across them. When we do it right, a workflow acts like an intelligent assistant that works behind the scenes to make sure things happen. And this is never more apparent than when it comes to tasks.
Nintex is laser-focused on getting tasks to users via the methods that fit them best.
Use the UI You Like
Nintex Workflow Cloud is deliberately UI-neutral. We’ve found that Salesforce users like Salesforce’s user interface, or third-party forms add-ins that mimic it. SharePoint Online users prefer a UI that behaves as a seamless part of SharePoint (e.g., Nintex Forms for Office 365, Nintex Forms for SharePoint Server, etc.). If you’re building a workflow that involves both, which forms provider do you use?
The right answer is “both” because we wouldn’t dream of imposing one on the other. We will put the task in the right place and let that environment render it properly. For a cross-product process, which is where the real action is, each environment gets the best-fitting UI.
Content Counts, Too
Bringing the work to a user’s preferred location isn’t just about tasks — it’s about content, too. Assigning a user a task to review or create something and making them gather necessary inputs from many locations? That’s annoying if not insulting. The workflow should be smart enough to do that. And when the unit of review is a complete document, Nintex document generation can take data, previous user responses, calculations, and any other input, and use them to generate brand-new content to give to users at the beginning, middle, or end of a business process.
Custom, Yet Contained
Finally, there are times when we should build a UI of our own, but even then, it’s meant to be used in a place users already visit. Nintex workflows can be started by anonymous web forms, in mobile apps, and by web service calls. In each of these cases, those forms are meant to show up in an existing website, a mobile app that already shows other work forms/tasks/statuses, or other complete apps that contact us behind the scenes.
To reduce user fatigue, to simplify the work of process designer and to increase the chances of a solution’s adoption, we’re meeting the user in familiar places. We think it’s a better way to work than app after app after app, and we hope you do, too.
For additional information, visit the Nintex Workflow Cloud webpage and related blog posts: “What’s New with Nintex Workflow Cloud”, “You, Zoe and Nintex Workflow Cloud,” and “Why’d We Build Nintex Workflow Cloud?” Nintex Connect, our community site, also has information on our cloud platform, release notes, how-to videos like the “How to Start a CRM Workflow in Nintex Workflow Cloud” video and blog posts about Nintex Workflow Cloud features, such as External Start.