Introduction
This post is part of my series on the journey from being an End-User to becoming Microsoft Partner-Side Consultant.
Moving from being a business applications end-user to joining a Microsoft partner organisation can be an exciting and rewarding journey.
The practical skills you have gained as a business applications end-user are a huge asset in the partner ecosystem. It’s important to recognise these superpowers and put them to use.
Applying soft and hard policy to business processes
As a business applications end-user, you will have gained a deep understanding of real-world business processes and workflows. This knowledge is crucial when transitioning to the partner ecosystem, where you will be expected to design and implement solutions that optimise similar processes for client companies.
First-hand experience of running real business processes through a business application like Dynamics 365 Business Central gives you important insight around the use of soft and hard processes.
There are always a number of ways to approach a process, knowing what works well, but most important what doesn't work well is key here. Most end-to-end processes will have both on-system and off-system elements, hard processes; those fully encoded by the application(s), and soft processes; those where there is an element of off-system processing or where users need to be aware of the correct process to follow in-system.
Clients looking to implement a new system are often drawn toward establishing a hard policy for their full end-to-end processes. Trying to create all end-to-end processes as hard processes is rarely a good idea. The most efficient end-to-end process will often include an element of soft process, where the users can flex - your experience as an end-user gives you the vital insight as to where best to allow soft vs hard processes.
Specific area technical proficiency
As an end-user your hands-on experience with business applications has likely endowed you with a high level of technical proficiency for a particular sub-set of operational areas. This might also include familiarity with customisation, integration, and troubleshooting, which are essential skills in the partner ecosystem.
Moreover, your technical skills are not just limited to understanding how the application works, but as an end-user you will have a considerable grasp of the overall process in the context of real-life day-to-day issues, which will influence how you approach and design process solutions.
In other application areas, you may not have much experience at all, if any. This is very normal for any consultant, so don’t let his hold you back. Be certain to identify the application areas you are weaker in and make a plan around learning. When approaching other for help, you will usually get a better reception if you have taken the first steps yourself, done the basic learning and had a try. Networking within the team & the wider org is important - find out those who you can help.
Start with the end (of the project) in mind
Working on the end-user side implementing new systems or processes for your colleagues has a subtle but important difference when compared with working as a consultant implementing systems for clients.
On the end-user side you implement change and then continue to work with your colleagues for the long term potentially. This means that, from the very start, you are likely considering (aka worrying about!) the post go-live ongoing operational situation. How happy will your colleagues be with the new processes / new systems, what is in it for them, how will you get as many people as possible around the change curve into the ‘happy with the change’ camp?
This post isn't about change management strategies, although that is a fascinating & important topic, instead I just want to highlight the subtle difference in approach you have been forced to adopt on the end-user side. Even if it was simply due to self-interest - you have to work with your colleagues in an ongoing timeframe after all!
Take this end-user ‘start with the end in mind’ focus with you as a partner-side consultant. When working on delivery projects for clients this approach can make a big difference to the overall project and in my view really contributes to the quality of the delivery work.
Conclusion
The transition from end-user to partner side partner consultant has many challenges, but you bring a wealth of knowledge and experience that can truly make a difference on projects for clients both within and outside of your industry area. Be certain to identify the business processes you need to work on, but also share with the team the processes you were familiar with in your end-user role. By identifying and capitalising on your end-user superpowers you can make a meaningful impact on projects, contribute to the quality of the delivery work and most importantly the on-going success of the client for the longer term.
What do you think?
Please let me know your thoughts in the comments
Connect or follow me on LinkedIn to get all my updates Andrew Wingate | LinkedIn