Monday, July 17, 2023

Microsoft authenticator backup; do it before stuff happens!!

 


As a technology driven professional, I backup my phone and computer data regularly. However, I recently encountered an issue with Microsoft’s Authenticator when upgrading from an iPhone X to iPhone 13. I did not realize that Authenticator data (the entries for each of my clients and my Microsoft accounts), was not included in my regular iPhone backup.

After restoring my iPhone X backup to the new iPhone 13 (a nice hand-me-down from my daughter!), the were no entries and therefore I lost all access to my clients’ systems and Microsoft accounts! Wow.

So, I faced the embarrassment of calling each client’s help desk to re-install the link for Authenticator. Plus, I had to create help tickets with Microsoft to regain access to my Partner Center, Azure and other accounts….not really all that much fun, despite the wonderful help I received from the Microsoft tech team.

Setting up Authenticator backup is fairly easy and Microsoft has a description of the setup for both iPhones and Android devices:

Backup and recover accounts with the Microsoft Authenticator app - Azure AD |Microsoft Docs

You can check the backup status by navigating on your iPhone to:

Authenticator > Settings


The main issue I had to complete the setup was turning on my iCloud drive. If yours is not on, and you get an “upgrade” selection when selecting to enable iCloud Drive that you cannot accept, then use a web browser to enable Keynote on your iCloud account:


 

Now, I am ready for another iPhone upgrade or in the worst case if I lose or damage my iPhone 13!

Hopefully, you can now avoid the time and embarrassment I encountered this week!

Wednesday, March 4, 2020

ERP implementation: who are you going to call?



With the reboot of the 1984 classic Ghostbusters movie being released this week, I have been reflecting about the tagline: “Who are you going to call?” Seems relevant to the consulting business where we compete for business and frequently ask ourselves how a customer intends to decide who to call (meaning which consulting firm to select). An Enterprise Resources Planning (ERP) project can a transform an organization and is not to be taken lightly, so an organization’s selection of an implementation partner is critical.

My experience is that customers take one of three basic approaches to decide “who to call”:

  •          Prepare and issue a formal request for proposal (RFP)
  •          Informally interview and obtain proposals
  •          Strategically work with an existing consulting partner to formulate the project


Many customers create an RFP to facilitate a well-defined decision process. The RFP contains the scope, requirements, selection criteria and response formats necessary to yield comparable proposals from 3 or more consulting organizations. These RFP may include thousands of requirements and many pages detailing the response format. The consultants respond with proposed implementation project details that the customer’s decision making team can compare to decide. Of course, there are steps for the customer and prospective consultants to interact with demonstrations and other meetings so the teams may clarify the RFP, answer questions, and get to know each other.

An informal or less structured process does not necessarily mean less rigor than the RFP. Customers may conduct numerous meetings and request software demonstrations to ascertain the fit the company’s needs and culture. A less formal process may take more twists and turns as the customer team learns from the consultants and pursues discussions and avenues to inquire. Ultimately, the customer makes a decision based on data, opinions, and steps some of which may not have been initially planned.

The strategic approach does not necessarily mean the consultant is not evaluated. For customers with an existing relationship or basis to focus on a primary consultant, the strategic evaluation focuses on the project definition and how the consultant adds to the cost/benefit/risk parameters of the project. Clearly the consultant must be qualified to deliver the project and the evaluation must focus on how the project can be delivered within risk and timing that achieves success. A strategic evaluation may bring the consultant further into the benefit and risk aspects of the project and not just the scope, approach, and cost.

So, how do consultants view these various different approaches? Unless the consultant wrote the RFP or has an inside track on the informal process, each has its own positives and negatives. Some viewpoints to consider for each approach:
  1.           RFP – the consultant does not want to be “column fodder”, so this concern should be addressed
  2.           Informal – spell out and communicate some reasonable steps and timing to conclude the decision so the consultant has an overall view of the process
  3.           Strategic – address differences in expectations and approach if the consultant’s relationship and past projects do not include technology and applications consulting

So is any one approach best? Maybe it depends on the company and situation. I have had experience with all three and both won and lost, so which process seems to be less of the prescription for success than the quality of the dialog between the parties and the agreements reached for the project to setup reasonable expectations on both sides for success.

But, setting expectations for success is another movie and blog post, so for now let’s suffice with the question: who are you going to call? And by the way, I will look forward to feedback on which version of the Ghostbusters movie is preferred: the original or the re-boot!

About Kirk:

During his 30 year consulting career he has led many ERP selections and implementations, primarily in the manufacturing, distribution and high technology industries. During a recent two year respite from consulting, he was an executive leading a global supply chain organization using Microsoft Dynamics. As the global supply chain director, he appreciated the opportunity to “eat his own dog food” by running the business processes and technology he helped the company select and implement.

Kirk’s published works include this monthly blog, magazine articles, conference presentations, and the book Lean Distribution, which focuses on the relationship between ERP and lean operations in the supply chain.

Workflow and the self-checkout lane



The other day, I was patiently waiting for help at the grocery self-checkout lane and began to wonder how this process may have similar issues to those that arise with workflow processes in an Enterprise Resources Planning (ERP) implementation. These “self-checkout” stations are designed to save the stores money and to add convenience for shoppers, but my observation is that fewer than half of all shoppers choose to use them. I prefer self-checkout, despite the frequent starts and stops due to the various weight or scan issues encountered, so I lean toward being a frequent user. Other shoppers avoid these lanes and prefer to have an employee perform the checkout. Frequent self-checkout users recognize some downsides to this automation:

  1.             Being behind someone who is unfamiliar with the technology who slows down progress
  2.            Scale checks for items with negligible weight (the bag platform scale cannot confirm the bag weight has increased and that the item was bagged)
  3.            Item purchase constraints to adults (alcohol, etc.)
  4.            For a grocery store, a produce item without a four or five digit item code (I cannot remember whether the item lookup for green peppers is under “G” for green or “P” for peppers)


For many of these exceptions, an attendant must be called to reset or over-ride the station, which somewhat defeats the purpose of the automation. So when I stand there waiting for help due an item weight not registering, I wonder whether the store really reduces shrinkage with these irritating weight checks (my assumption of the purpose for checking the weight of each item scanned)? My observation during a recent Walmart visit is that an attendant can monitor and support close to 10 stations, so there must be labor savings for the stores. Anyways, that is the policy and how the systems were programmed, so we are stuck with it.

So what does this have to do with workflow? Well, workflow has both admirers and critics for similar reasons, so it may be interesting to see how organizations either adopt or avoid workflow during an ERP implementation. Since many people are familiar with self-checkout, it makes an interesting comparison.

For those considering workflow controls for business processes the objectives typically are to streamline processes while enforcing adherence to policy. So workflow performs various checks and approvals required for specific transactions, such as a purchase requisition. A sample business process may be something like this:

  •          User initiates a requisition for a new chair, since their current one is old and broken.
  •          The user is presented a selection of chairs that may be selected
  •          Once the requisition is complete, the user submits to workflow
  •          A budget check is performed and if the department budget has not been spent, the requisition proceeds to the manager; if the budget is spent, then the requisition is returned to the user.
  •          The user’s manager receives the requisition with a workflow action to approve
  •          Manager may approve, reject or request modification.
  •          There may be dollar limits for manager approvals that require additional approvals or may be approvals to procure certain groups of items.
  •          Once approved, the requisition is routed to Finance to check for proper tax and department coding.
  •         After Finance approval, Purchasing receives the requisition and can auto-create a purchase order to the appropriate vendor. If the item price was incorrect on the requisition and the budget check is no longer satisfied, then the requisition is returned to the user


This is a rather simple workflow example that is one of the most common. For the workflow to succeed the following data must be accurate and complete in the ERP system:

  •       Department budgets
  •       Organization hierarchy
  •       Current departmental expenditures, including open encumbrances (Purchase orders, etc.)
  •       Vendor catalogs: items, allowable items, and prices
  •       Workflow rules for escalations
  •       Personnel in the organization who review or approve transactions may require an ERP system license


So what can go wrong? The vendor catalog, prices, and budgets must be right. But also consider that delegations to alternate approvers must be setup for vacation and other absences for a department manager, Finance, and Purchasing buyers should be setup to route the requisition without delay. So for a new chair small delays may not be a concern, but for other transactions workflow delays may create problems most users are ill equipped to address. Chasing down this requisition within the workflow should be easy and corrective action straightforward, but this may not be the case.

So how do workflow processes relate back to the self-checkout lane? First, the constraints (like budget available) must be readily verifiable. If department budgets are not accurate or up to-date, then many exceptions may occur or expenses approved in error. Second, there must be ready access to override absences and other workflow stoppages by team members with the visibility into the workflows and authority to take action. Third, there should be metrics and reporting to visually identify the status of all workflows in order to adjust workflow parameters to maintain the proper balance between tight controls and acceptable numbers of exceptions, like the roving checkout attendant who looks for the red light on top of a station or a bewildered customer with an issue. Lastly, the organization hierarchy should be specified using titles wherever possible to avoid workflow changes for each change in personnel and role.

Coming back to the self-checkout lane, what improvements would we like to see? The store should skip weight checks on items with negligible weight. This one change would reduce a lot of errors and time spent waiting for the system and then requiring an override (either the “I do not want to bag this item” selection or an attendant). Improve the bag supports so it is easier to place items in your own bags, since the frames are primarily designed for the store supplied plastic bags and do not readily accommodate customer supplied bags. The focus should be on customer convenience and not auditing to the detriment of the customer experience.

For workflows, designs should balance policy enforcement with ease of use and organizational efficiency. Start with some limited controls and routes in order to minimize complexity. If the workflows are complex at system go-live, there may be too many exceptions and work may grind to a halt! This is the concern I hear most frequently and spend the most time addressing during an implementation.

I have had clients with both numerous workflows at go-live and those who delayed implementing workflows until after the initial implementation was stabilized. If you do go forward with many workflows, especially complex ones, extensive testing for the organization hierarchy, security roles and exception scenarios should be included prior to user acceptance and go-live. Just keep in mind the self-checkout attendant on a busy Saturday!


About Kirk:

During his 30 year consulting career he has led many ERP selections and implementations, primarily in the manufacturing, distribution and high technology industries. During a recent two year respite from consulting, he was an executive leading a global supply chain organization using Microsoft Dynamics. As the global supply chain director, he appreciated the opportunity to “eat his own dog food” by running the business processes and technology he helped the company select and implement.

Kirk’s published works include this monthly blog, magazine articles, conference presentations, and the book Lean Distribution, which focuses on the relationship between ERP and lean operations in the supply chain.

ERP Requirements: a Paradox?


I had the difficult task recently to respond to several potential customers’ requests for proposals (RFP) that included numerous business requirements for an Enterprise Resources Planning (ERP) system. These RFPs contain from hundreds to thousands of requirements vendor organizations are expected to respond with a fit or gap. These companies are selecting an ERP application and implementation consultant based on these responses. It struck me that most organizations rarely write well-constructed requirements. This results in requirements that are difficult to follow, confusing, or may be too easily answered as a "fit".

The objectives for an RFP seems clear: obtain the best “fitting” and implemented information system at a low cost to benefit ratio. Well, that is what I typically assume is the objective. There are organizations that seek the lowest cost alternative, or at least they believe a lowest cost decision can be made based on these criteria. What may be challenging to evaluate is how fit/gap responses on requirements link together to achieve benefits across a specific business process and whether the responses from vendors will yield an application meeting those needs.

The first key is to articulate the requirement.  This seems to be a basic and easily achieved step, but this is frequently not the case. A requirement “Barcode data capture at Receiving”, communicates the idea that using bar codes is desired, but leaves a lot of room for interpretation. Is the purchase order number scanned? Or are the item numbers scanned?  Does this relate to printing a document with a bar code? Alternatively, this could be scanning all of the batch or serial numbers for the items after receipt. This bar code requirement does not articulate a complete actionable and measurable need. Each requirement should be one concept where a fit/gap response can be subsequently demonstrated and tested.

If the objective of the bar code requirement is to simplify and automate the receiving process, why not ask for ideas on how the application accomplishes that objective? For example, I might respond that vendors could send an advanced ship notification (ASN), which could be scanned to initiate the receipt of the purchase order lines and quantities, rather than the user taking five steps in the process: find the purchase order, enter the packing slip number to initiate the receipt transaction, review all lines on the purchase order, select the appropriate lines, and possibly edit the quantity received on each line. With an ASN, Receiving scans the vendor’s packing slip number and then confirms the physically received items and quantities for an exception based receiving process.

Articulating requirements takes a degree of precision and tenacity to be clear, concise and complete. It takes more effort to be concise: as Thomas Jefferson famously said (“I’d write a shorter letter but do not have the time”). Let’s address these three elements of a well written requirement:

  •            Clear: addresses one concept and includes a noun and a verb.
  •           Concise: uses few words with a separate glossary to clarify acronyms and company specific terms.
  •          Complete: the requirement may be tested and validated at multiple points during the implementation to insure the solution is adequately designed and accepted.


Once the requirements are well written, consider grouping some of the most critical requirements along the lifecycle of a process.  Displaying the sequence of requirements needed to accomplish a process objective enlightens and clarifies the relationships between requirements. Use a process flow diagram with referenced decision and action points. Back to the receiving process, we can display the As-Is and To-Be processes, articulating that two time consuming and error prone steps are eliminated:  “Enter PS# and start receipt” (enter the packing slip number and start the receiving process in the ERP system) and “Edit lines & quantities” (remove lines not received and change the quantities of lines the supplier partially shipped):


Even with this simplified business process flow (it only shows the “happy path” of a correct receipt), the benefits of eliminated steps is clear and these requirements for the To-Be process are articulated:
  •       The vendor ASN must include a unique packing slip number as the key
  •       The ERP application creates a “pending” receiving transaction for each ASN
  •       The user scans the vendor packing slip number (which must be in bar code format) to initiate the receiving process
  •       The user should manually validate the correct items and quantities received and may code the transaction as not matched
  •       Process steps outside of the ERP application may be shown (dashed boxes in the graphic above)
  •       Printed documents from the ERP may be shown (e.g., receipt traveler)


An alternative to the ASN process could be to scan the entire vendor packing slip and use optical character recognition (OCR) to translate the packing slip into text and initiate the receiving process. Depending on the application’s functionality and customer’s needs either the ASN or OCR alternative may be the better approach, since there are positives and negatives for both:

Approach
Positives
Negatives
OCR vendor packing slip
Can be used without vendors changing their processes
Packing slips may not scan successfully or consistently
Vendor sends ASN
Provides advanced notice of shipment for inbound receipt planning
Can identify issues prior to receipt (partial ship, etc.)
Vendor processes to send ASN & packing slip in prescribed format
Requires a manual process for vendors without ASN
For this receiving example, the organization may 
now have an alternative it had not considered or even knew was possible, so the costs, benefits and risks of each may be assessed.

The additional time and effort to articulate requirements provides the clarity between the project team and the vendors responding. It may even make the job of responding more difficult by eliminating those pesky assumptions for requirements used to interpret requirement most favorably for their solution!

About Kirk:

During his 30 year consulting career he has led many ERP selections and implementations, primarily in the manufacturing, distribution and high technology industries. During a recent two year respite from consulting, he was an executive leading a global supply chain organization using Microsoft Dynamics. As the global supply chain director, he appreciated the opportunity to “eat his own dog food” by running the business processes and technology he helped the company select and implement.

Kirk’s published works include this monthly blog, magazine articles, conference presentations, and the book Lean Distribution, which focuses on the relationship between ERP and lean operations in the supply chain

ERP Selection: Overstuffed like Thanksgiving?



Whenever the Thanksgiving holiday approaches in the US, I wonder whether Enterprise Resources Planning (ERP) selection teams are “overstuffed” with requirements. Like my tendency to over eat on the holiday, are there ERP teams attempting to digest a “laundry” list of requirements from their business users as the selection process proceeds? Are these lists beneficial or does the very “wish list” nature of many requirements detracts from the main criterion for success: picking the most appropriate application? I have responded to requests for proposals with 1,000 plus requirements; in some of these projects the selection tended to focus on all of the gaps at the expense of the overall business transformation desired.

Business users are asked for their requirements, but rarely for how critical new business goals or transformation will be achieved. When someone says, “the system must be able to explode a BOM and ship components on a sales order”, the requirements seems clear and concise. But, do we really need a bundle (a specially designated BOM for this purpose) or can the sales order have one item that generates additional line items at no cost or at the customer’s price? Is the requirement to have the customer order one item and have multiple ship or have the customer order one item and the warehouse creates a group (kit) of items as those items are picked and shipped as one? If the users are not careful and objective driven, the requirement may be defined based on how the existing system was designed and new process alternatives may be missed.

Back to overeating on the holiday scenario, why does this happen? For me, Thanksgiving is a once a year opportunity to have turkey, dressing and cranberry, so I tend to eat too much. Like Thanksgiving, many ERP selection teams are given one opportunity to raise requirements and list their needs for the new system. This may add to the urgency users feel to throw out all types of issues and needs rather than focus on priority requirements.

So how do we break the cycle of overloading on requirements while under the gun of a tight ERP selection time frame? One approach is to start with the samples of the beginning and end documents and reports for business processes. These reports and documents can be used to identify the key requirements and provide examples of key existing functionality and bring some otherwise generic needs to life. Let’s address a couple of examples:

  •  Customer purchase order - are these channel partner orders where the end customer must be tracked? What data must flow from the customer PO all the way to the invoice, such as the PO and line number?
  • Sales order confirmation – are these sent to the customer or only used internally to check accuracy? For a customer facing version, the content can identify data and process requirements, like the link to the customer’s PO number and version.
  • Sales order packing slip – do some customers have specific requirements to aid in their receiving process such as serial number bar codes? Are there bundles or kits with the components shown or hidden?
  • Sales order invoice – what is the frequency to issue? Does the customer have a centralized accounts payable function? Are there required customer account codes such as budget codes or general ledger accounts?


For each key document, a sample should be collected for each variation (e.g., different by customer or customer segment, etc.) to show the events and data driving variation. Customer and regulatory requirements are key here, but how variations are managed is as well. By taking samples or desired end results, the selection can focus on the processes necessary to achieve those goals.

Most companies have complexity that is important to manage and requirements help to assess whether each ERP solution will be a good fit. What must be added to the conversation and analysis are the perspectives on managing differently that transcend any one requirement to provide the visibility into the new process approaches necessary to drive change and enhanced business results.

About Kirk:

During his 30 year consulting career he has led many ERP selections and implementations, primarily in the manufacturing, distribution and high technology industries. During a recent two year respite from consulting, he was an executive leading a global supply chain organization using Microsoft Dynamics AX. As the global supply chain director, he appreciated the opportunity to “eat his own dog food” by running the business processes and technology he helped the company select and implement.

Kirk’s published works include this monthly blog, magazine articles, conference presentations, and the book Lean Distribution, which focuses on the relationship between ERP and lean operations in the supply chain.

ERP Phase 2: Trick or Treat?



Are there similarities between Halloween door to door “Trick or Treat” and staff arriving at an executive’s office after an ERP (Enterprise Resources Planning) project goes live with requests for system enhancements? Although there may not be as many costumes involved in the work environment, an executive cannot be certain whether the request must be denied (a trick results) or a system change can be made (a treat provided). With some of both encountered, how do you ensure the organization moves forward effectively without breaking the support budget to avoid tricks?
Minimizing tricks starts with managing the remaining scope and budget commitments from Phase 1. During the Phase 1 project requests for work excluded from the original plan may be deferred to a “Phase 2”. These scope deferrals should have been evaluated, estimated, and documented in the project environment such as Microsoft’s TFS (Team Foundation Server). As these Phase 2 items are raised, the TFS details should be referenced and updated based on current priorities and investments. For scope deferrals no longer required or desired, budget may be freed up for new items. In this way the Phase 2 budget may be monitored and new items categorized and evaluated without re-inventing the overall project plan and budget.

New items raised that are not in TFS from Phase 1 should be addressed as opportunities. Assuming these items require a system enhancement, there should be assessment of the impacts to current processes, configurations, data, and code. No enhancements should be made without a thorough assessment. Some considerations for the various additions may include:
  •  Reports – these are new or changed screen forms or printed data. Assess whether this is still a requirement or just replacing a report that is (or was) infrequently used? Have existing standard reports and inquiries been completely reviewed for fit? Is there a user based option to obtain the data such as export to Excel or a user based “ad hoc” report?
  •  Printed forms – changes to forms such as invoices, orders and other external facing documents. Check the external requirements and challenge internal ones. For infrequently used documents assess options such as exports to Word or Excel to create an acceptable format.
  • Data validation – these are requests to reduce data entry errors. The code to add system edits or user selections may reduce errors, but may also have unintended implications such as limitations to future flexibility to thoroughly assess.
  •  Data entry automation – these are requests to eliminate “clicks” required by the user and can improve efficiency. Validate that the process is required and whether the process metrics are being achieved and whether further improvements are cost justified.
  • New requirements – changes to configuration and systems to meet new requirements from the business. The approach for these changes should be evaluated against the current and other standard functionality available prior to initiating enhancements. In some cases the team members may not fully understand other functionality that could meet the requirement which the consulting team may provide with demonstrations.


The short answer is to plan and prepare for the Phase 2 requests during Phase 1. The plan should include budgeting Phase 2 and assessing scope items when the initial deferral decision is made. Setting expectations with your team are critical to managing new items to the budget and return on investment.

As we carve the Halloween pumpkins and put out decorations for the arrival of those fun costumed visitors, executives should keep in mind how they give out “Treats” as well as how they turn “Tricks” into opportunities during the Phase 2 of their ERP project.

About Kirk:

During his 30 year consulting career he has led many ERP implementations, primarily in manufacturing, distribution and the high technology industries. During a two year respite from consulting, he was an executive leading a global supply chain organization using Microsoft Dynamics. Kirk published works include a book Lean Distribution, which focuses on the relationship between ERP and lean operations in the supply chain.


ERP “Heart” Transplant: Post-Op


Just back from two weeks assisting my client go live on Dynamics. This was a successful transition from a character based ERP (Enterprise Resources Planning) system to the new world of Microsoft Windows and Dynamics. There were small bumps along the road, but overall go-live went very well and our client was confident ending our on-site support after only two weeks.

This brings me back to the surgery and heart transplant analogy. Our client’s enterprise systems were off line for a couple days as we converted data and prepared the production system. Similar to a heart transplant, this “downtime” is a critical when the old heart (the legacy ERP system) is stopped and removed. Like a surgical team, our client team performed admirably and was well prepared for the Monday morning go-live when the new “heart” (Dynamics) was brought on line.

Post go-live with ERP is very different than the time in surgical post-op recovery. With ERP, our client must ramp up to full operations immediately. There is no time to rest, slowly recover and take on activity as your health allows. Business processes and operations must run at 100 percent on day one! For our client this meant completing all shipments for the quarter-end within days of the go-live using the new business processes and Microsoft Dynamics.


Winding down our consulting support does have some client team members concerned. As in the post operation recovery room, the ready availability of medical professionals is comforting. For ERP, this means access to help when some unfamiliar transaction warning arises or a rarely used process is performed. An analogy is the scene from near the end of the movie The Matrix when Neo is running down the street, calls the Nebuchadnezzar (the Operator is Tank), and says, “Get me out of here mister wizard”. So my parting words to the client team members were to not worry, since we are just a Skype call and screen share away! 


So what is next? I plan to take a couple of weeks off, play with some new features of Microsoft Dynamics, and prepare for the next client. Oh, and keep my Skype ans Teams status “Available” so “Mr. Wizard” is always just a screen share away.

About Kirk:

During his 30 year consulting career he has led many ERP implementations, primarily in manufacturing, distribution and the high technology industries. During a two year respite from consulting, he was a hands-on Microsoft Dynamics AX user leading a global supply chain. Kirk published works include a book Lean Distribution, which focuses on the relationship between ERP and lean operations in distribution.


Your (enterprise) “heart” is in our hands



I am on my way to a client location for an Enterprise Resources Planning (ERP) go live this week which I at times refer to as a “corporate heart transplant”. If you are familiar with an ERP implementation project, then I am sure you will see an analogy to heart transplant surgery:  for this enterprise, the client’s heart (all of their enterprise data) is disconnected and the company’s operations are halted this weekend as the conversion is underway. So in a way, their “heart” is in our hands this weekend as we are converting data and preparing the systems for the “go live” Monday morning.
 
I use the heart surgeon analogy (with all due respect for doctors and nurses), because many times I sense my client’s concern and angst as they go into the final phase of the project and realize that the fate of the business can ride on the next few days. Like the patient who knows their beating heart must be stopped, replaced and re-started, this requires complete confidence in those around you in the operating room. While I have been in a hospital operating room six times undergoing procedures in my life, none have been as life threatening as a heart replacement. At each time I was confident in my surgical team, so I can only begin to appreciate someone going into that operation: they must have full confidence in their surgeon and her/his team!

While going through an ERP go live may not be life threatening to the people in an organization, it certainly can threaten your career. I know people whose careers were impacted due to ERP project failures, and picking up those pieces is not much fun! Like the patient, you must have full confidence in the consulting team, the ERP application, and your internal project team members. Everyone must be committed to success. But how do you really know it will all turn out well? We have checklists and plans and tests and demos galore, but at the end of the day it must work and your employees must be able to run the organization with the new business processes.

Consultants differ in approach to the ideal ERP project implementation. Some may say scope and detailed requirements must be locked down at the beginning of a project and relentlessly managed to be successful. I am not so sure it is realistic to stop all business change for a year or more while a new system is planned, designed, built, tested and employees trained. Organizations must continue to adapt to change and business processes being designed with the new system may identify opportunities for competitive advantage. So there is no simple solution in my view, except the project must retain a balance between risk, scope, benefits, time, and resources. Your consulting and internal team are critical to making this journey achieve success and I am convinced that building the business process delivery excellence into the system design and organization throughout a project are the way teams insure a successful go live.

As I contemplate this latest journey, one of my next tasks is to put my keyboard back to work and write some of my thoughts on the topic. What do you think? What successes and challenges have you experienced on these lengthy (typically a year or more) journeys to new business processes and systems with ERP?

In the meantime, I look forward to the next couple of weeks as we help our client transition to their exciting new world of business processes and information technology using Microsoft Dynamics AX 2012.

During my 30 year consulting career there have been many and each was unique and special in the bonds built with my client and the rest of our consulting team. I both look forward to the go live and feelings of loss as the relationships invariably begin to fade and I move on to the next project. But at the end of each there is definitely a “sigh” of relief, pride of accomplishment for what has been done, and time to rest.

I am on my way to a client location for an ERP go live. During my 30 year consulting career there have been many and each was unique and special in the bonds built with my client and the rest of our consulting team. I both look forward to the go live and feelings of loss as the relationships invariably begin to fade and I move on to the next project. But at the end of each there is definitely a “sigh” of relief, pride of accomplishment for what has been done, and time to rest.

If you are familiar with an Enterprise Resources Planning (ERP) implementation project, then I am sure you will see the heart surgeon analogy: for this enterprise their heart (all of their enterprise data) is currently in our hands and the company’s operations are halted this weekend while this conversion is underway. So in a way, their “heart” is in our hands this weekend as we are converting data and preparing the systems for the “go live” Monday morning.

I use the heart surgeon analogy (with all due respect for doctors and nurses), because many times I sense my client’s concern and angst as they go into the final phase of the project and realize that the fate of the business can ride on the next few days. Like the patient who knows their beating heart must be stopped and replaced, this requires complete confidence in those around you in the operating room. While I have been in a hospital operating room six times undergoing procedures in my life, none as life threatening as a heart replacement. At each time I was confident in my surgical team, so I can only begin to appreciate the foreboding facing someone going into that operation: they must have full confidence in their surgeon and her/his team!

Going through an ERP go live may not be life threatening to the people in an organization, it certainly can threaten your career. I know people whose careers ended due to ERP project failures, and picking up those pieces is not much fun! Like the patient, you must have full confidence in the consulting team, the ERP application, and your internal project team members. Everyone must be committed to success. But how do you really know it will all turn out well? We have checklists and plans and tests and demos galore, but at the end of the day it must work and your employees must be able to run the organization with the new business processes.

Consultants say scope and detailed requirements must be locked down at the beginning of a project and relentlessly managed to be successful. I am not so sure it is realistic to stop all business change for a year or more while a new system is planned, designed, built, tested and employees trained. Organizations must continue to adapt to change and business processes being designed with the new system may identify opportunities for competitive advantage that cannot be ignored. So, there is no simple answer in my view, except the project must retain a balance between risk, scope, benefits, time, and resources. Your consulting and internal team are critical to making this journey achieve success and I am convinced that building the business process delivery excellence into the system design and organization capability throughout a project are the way teams insure the go live goes well

There may be many other theories and opinions on how to be successful with an ERP project, so one of my next tasks is to put my keyboard back to work and write some of my thoughts on the topic. What do you think? What successes and challenges have you experienced on these typically year or more journeys to new business processes and systems with ERP?

In the meantime, I look forward to the next couple of weeks as we help our client transition to their exciting new world of business processes and information technology using Microsoft Dynamics .