It’s not often that Microsoft holds a webinar where they cover so many upcoming Microsoft Dynamics 365 features that are in preview (unless it is shown under the cover of a nondisclosure agreement). But in late June, it was like Dynamics Festivus came early.
There were many exciting details shared during the June “Executive Briefing” from Microsoft…but it also left some questions.
With the upcoming release of Dynamics 365 (9.0) there will be two different flavors of Dynamics 365
(If you’re using Dynamics 365 today–July 2017–you have Enterprise Edition)
Okay, that might not seem like that big of a deal, so allow me to elaborate. The Business Edition will be released with a greatly improved user experience (called the “unified client”) for web, phone, and tablet which comes with a grip of improvements over the current experience. There are many more features that will be available for Business Edition customers when it is released.
If you’re on Enterprise Edition today, you can’t just switch to Business Edition. This means that some new features will be immediately available to Enterprise Edition clients (including notable things like the unified client.
You might not want to anyway (even if it were allowed) because there will be some limits imposed in the Business Edition. Things like a limit of the total number of Users, Account records, and custom entities (with specific details to come).
The custom entity limit is a bit misleading, though, since it appears that the entities in apps available through AppSource will not count against this total. Effectively, this message is to look for a chance to buy an app instead of rolling-your-own when it comes to meeting your requirements.
If you’re an existing Enterprise Edition client…there’s a pretty good possibility the answer is “no”. Plenty of clients may have a low number of users, but the record limits and custom entity limits will likely cut down the number of people who would even be able to consider the change. Not to mention that it would be a separate instance of Dynamics that would need to be configured and have data migrated to it.
Instead, I think most Enterprise Edition customers should look forward to getting features as they’re made available (and keep your eyes and ears open for the Private and Public Previews that Microsoft mentioned).
If you’re still considering the Dynamics platform–then the Business Edition will have a lot to offer as you get rolling (and an upgrade path to Enterprise in the future).
Are you considering Dynamics 365 Business Edition in your organization? Share what you’re most excited about in the comments!
How do you get past those little barriers that keep you from doing the things you know you should do? Joel and Matt talk about how they try to deal with this.
Do you feel like you could get more out of your meetings? Joel Lindstrom and Matthew C. Anderson cover their top 3 tips for hosting productive meetings.
OneNote has been around for well over a decade…are you using it to its fullest? Joel Lindstrom picks Matthew C. Anderson’s brain on some ways to manage your OneNote notebooks.
Were you disappointed by Microsoft’s announcement about the future of Wunderlist and To-Do? Joel Lindstrom and Matthew C. Anderson have an open therapy session and figure out how they’ll move forward.
How do you figure out how much time you spend in meetings? Responding to email? Working after-hours? Joel and Matt dive into Microsoft MyAnalytics.
How do you take care of some email now…without getting an immediate (and unexpected) response? Joel and Matt talk about living in the future.
According to the Atlassian, the average employee has 62 meetings per month and reports that half of those meetings are a waste of time. It’s great if you can reduce that total number but for the ones you do have, try to make them more effective meetings. I have several strategies I use to make the best use of my meeting time.
That said, one of the biggest time-sucks wasn’t just the time spent in the meeting itself, but post-meeting trying to put together summary emails that would go out to my team. It seemed like writing those summary emails would take as long (or longer) than the meeting itself! Does this sound familiar?
I knew there had to be a better way.
That’s when I changed up my process and started writing the summary email before the meeting even took place. At first, this seems crazy (or presumptuous at best) but stick with me, it’s only a draft at this point.
This draft becomes a reminder of what the important topics are and is a reference point to gauge progress during the meeting. As the conversation takes place, I amend my notes to reflect the actual discussion and can add more details where appropriate.
Below are the steps I use, which I offer here as a starting point.
The genesis of this idea is a simplified version of the “begin with the end in mind” concept, which is Habit 2 from Stephen Covey’s 7 Habits of Highly Effective People. The idea is to start thinking about the actual discussion that will take place, which serves a dual purpose of getting your mind focused on the meeting while giving you a chance to gather your thoughts on each topic.
Doing this is easiest if there’s a clear agenda for the meeting. This becomes a basic bullet point outline. Next, fill in the outcome you want to drive toward (or, if you aren’t exactly sure what you want, jot down the options you expect to discuss).
This doesn’t need to be exhaustive but it should be enough so that if you sent it out as-is you would have a little something to say about each topic.
Now you have your summary email drafted.
When the meeting begins, this draft will be an easy reminder/reference point for each of the planned topics. What’s become apparent to me in using this method is just how much “drift” happens during well-intentioned meeting discussions.
It actually becomes easy to see when things have drifted off topic. If something is way out of context with the summary you’ve prepared, consider putting the conversation in the parking lot until the core agenda has been addressed.
During the meeting, it’s easier to take notes because a decent chunk of the work has already been done. Sure, not everything will go exactly how it was laid out in the draft, but I find it to be a lot easier to make note of where things change rather than have to capture everything from raw.
The notes fall into two main categories:
When something is radically different from what I expected, it’s very recognizable, and it’s also much easier to make a logical appeal, rather than an emotional one. This is because I’ve already gathered my thoughts and can articulate what I expected based on my summary draft. This helps drive more effective meetings.
Additional details mostly focus on:
Also notice here how the burden of writing/typing during the meeting is reduced. This helps drive focus on participating in the meeting rather than being stuck using that brain power to figure out which notes to take.
I need to point out the elephant in the room: I don’t intend for this method to be interpreted as a way to railroad a meeting toward the outcomes you’re looking for. The point is to get your thoughts straight so you can focus on getting your point across as well as guide a productive session.
Another note is that this approach isn’t applicable to every type of meeting. It assumes some level of control to know what the meeting is about as well as forming an initial opinion on limited information.
Also, consider the audience and the importance of having some off-topic discussions. These can be really valuable, and remember that, sometimes there are important parts of the conversation that should have been laid out in the agenda (but weren’t).
Do you think that writing this kind of summary could help drive more effective meetings? Let me know in the comments!
When deploying or upgrading a relationship management system, success of the project often hinges on people actually using the system. In fact, according to the February 2016 Forrester report, CRM Success Hinges On Effective Change Management, 46% of those surveyed Agree or Strongly Agree that user adoption struggles were encountered during their CRM implementation. This is where Learning Path can help.
With Microsoft’s recent addition of Dynamics 365 release of their customer engagement capabilities (sales, service, and marketing) they have included a killer tool for providing the right help/reminders at the right time: Learning Path for Dynamics 365.
Deployments of Microsoft Dynamics 365 typically include configuration. You add fields to forms and update business process flows to support the way your company operates. These updates make the system speak your language and drive your processes—and these are exactly the things that should be reinforced inside of the system (without having to search for documents held in a different system or dig around for printout reference cards).
Dynamics 365 Learning Path provides this personalized step-by-step help. Users are literally walked through a scenario with guidance on where to click and what type of information to enter.
A key enabler is that this guidance can span multiple pages. For instance, moving through a sales process may involve work with a Lead, Opportunity, Account (etc.) and part of learning this relationship is to move between records at the right time. Learning Paths allow you to show how and when to move between records.
It’s also worth noting that once users are comfortable with using the system, they can opt-out of this guidance. This means people won’t feel “nagged” about how to use the system after they’ve become familiar with it.
Walk-through guidance on its own is helpful up to a point but sometimes you’ll need to provide additional reference material. There is a balance between the amount of content on the page and the depth that people might need.
Too much information with every step can make an otherwise simple system seem cluttered and confusing. Learning Path has a great way to handle this with an expanding sidebar where you can provide this self-service material.
– Links to other content (e.g. SharePoint content)
Training and communication are important aspects of driving effective change in an organization and Learning Paths provides ways to engage with users right inside of the application. There are plenty of uses, but here are a few examples to get the ideas flowing.
Set up walkthroughs so users can follow along during initial training (and reference them later) – This is especially helpful when users are very unfamiliar with both the system and the process. It’s also a great way to help in training where there is a high student to instructor ratio.
Use Learning Path when introducing new or updated processes – As usage of the system grows there will undoubtedly be tweaks made to the way information is displayed on the form or how the business process flow progresses. Offer new and updated Learning Paths to help support these changes.
Create role-specific content when it’s useful – Learning Paths recognizes who the individual user is, providing them the appropriate context based on their security roles. So, for example, when looking at a Contact record a sales rep and customer service rep could see different content that helps them with different processes and key information relevant to their role.
Regularly update sidebar content to include answers to frequently asked questions – the nature of learning paths makes them a great first-stop for this kind of information. Make this an easy (and in-context) place to provide answers to FAQs
Embrace the configurability and personalization of Learning Paths and iterate, iterate, iterate! Even well-planned changes will have bumps in the road—don’t look at these as static content. Consider including a link to submit questions if your current content doesn’t cover something.
This post originally appeared on the RBA blog.
Is procrastination sometimes a good thing…or is it always bad? Joel and Matt don’t put off talking about this one.