14
Mon, Oct
6 New Articles

Forget Technology: Solve Your Business Problems First

General
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Create a Business Design Document

Prepare a document as a blueprint for the project, identifying goals, processes, responsibilities, and measures. Working from a document that defines the scope of the project is a necessary tool; it validates agreement from those involved internally and is invaluable when discussing your needs with potential vendors and when measuring results. Such a document provides the opportunity to officially define project roles and responsibilities, which gives both direction and accountability. Specific components are associated with creating a usable business design.

Detail Project Goals and Expected Changes

·        Detail current and updated workflow with expected improvements.

·        Designate a level of importance for each feature and function impacted.

Identify Project Roles and Responsibilities

·        Select a project sponsor responsible for serving as a liaison between project leaders and the company's executive body.

·        Determine the role each department will have in the implementation project and identify the assigned project contact.           

·        Assign an overall project leader responsible for keeping the project moving forward.

·        Set forth implementation milestones, often designed around business drivers, budget, and decision timelines.

Outline Expected Cost-Justification for the Project

In order to calculate cost savings, during the discovery meetings it is important to assign a scribe to notate areas where costs could be eliminated or reduced by deploying the proposed changes.

 

The creation of such a document can be accomplished by following the "Seven Critical Steps for Technology Implementations," outlined below. Note that although they're listed in linear fashion, it is common for organizations to go back and forth among the steps until they have fully explored all questions and drawn out what they believe is a comprehensive business design. Use the process to your advantage and let it serve as a guideline.

Research and Analyze

Project leaders must fully understand both the problem to solve and the end-to-end processes and functions targeted for change.

1. Understand the Problem

Jumping in and buying technology before fully understanding the business problem along with its related processes and other factors impacted by the proposed tool will almost certainly lead to sub-optimal results. Analyses of the problem and process should be documented not as they are perceived by executives, but rather as they are actually practiced by front-line staff. It takes time and effort to collaborate both intra- and inter-departmentally to update current business processes and develop concise goals for the project. A success model for a technology implementation involves clearly identified steps.

2. Identify Goals and Requirements

In addition to identifying project goals, it is equally important to establish why changes are being implemented. Investing time to ensure that the reason for the project is clearly identified will provide significant benefit in getting organizational buy-in and realizing the anticipated outcomes. Many times during the discovery steps, such as while mapping current processes, the goals and requirements change, but it is important to start by asking and answering key questions:

 

·        What are the manual steps in the process?

·        Can the process be automated?

·        Can the process be centralized?

·        How are critical business documents (e.g., purchase orders, invoices, checks) being handled, and are there areas for improvement?

 

·        How are checks signed?

·        Who needs to review and approve POs and invoices?

·        How do you file and retrieve the documents and information?

3. Map the Current Process

Walk through each step with those who routinely follow the process. A full understanding of the "real" workflow up front is crucial in selecting the right areas for focused improvement efforts. The same questions you asked in the previous step should also be asked here, as they relate to your pain points and the way you do things today.

 

Identify touch points. Evaluate how selected processes and functions interact with other areas of the business. Reach out and ensure there is complete understanding of the interaction and determine whether it is currently working or in need of modification. Assess systems/software that are utilized in the current workflow and meet with those people responsible for managing them internally, as well as users, to fully understand how the systems/software integrate into the overall process. Gaining full understanding and consensus among all team members will help ensure adoption of the ultimate solution.

4. Design the Solution

A good brief will not only validate the workflow in its "current state," but also paint a picture of how the proposed solution will save steps and improve the process. The solution design can be either a list of how the steps in the process will work or a flowchart (usually the chosen method) depicting the ideal scenario.

 

Dare to dream! To paint a clear picture of the desired "future state," it is essential to allow a forum for free-flowing ideas without being limited by specific software functionality or hardware limitations. Collaborate with front-line staff and managers to explore how the proposed changes should modify the current business flow, and fully document expected improvements. Note areas of anticipated productivity gains in terms of staff time saved, shortened time to deliver goods and services, and/or an increase in production volume of goods and services.

5. Calculate ROI

Once a design is sketched out, it's time to associate numbers with anticipated areas of cost savings. Here are some examples:

 

Hard Savings

 

·        Business operating costs

·        Reduction in infrastructure costs

·        Increased in productivity measured by man hours saved

·        Increased cash flow

·        Reduction by attrition or flat growth in personnel

 

Soft Savings

 

·        Improved customer service (higher customer satisfaction)

·        Better and faster access to information

·        Faster internal communications

 

 

Determine timeframes for realizing identified savings and create a spreadsheet to include in the document. A comprehensive ROI will be calculated once a full evaluation is completed with the chosen vendor partner.

6. Document and Present

This step helps solidify the ideas, goals, analysis, and all other steps taken in the project. Revisiting the project gives other people an opportunity to review the business design as a whole (some people may have participated in only parts of this process) and ensures everyone is on the same page. Once a vendor is selected, this document is used as a tool to hold the solution provider accountable.

 

Investigate solution providers that can meet requirements outlined in the business design document. What you should look for is a solution provider you can establish a partnership with. This means you both have high stakes in the successful completion of the project and fully understand the goals, requirements, and expected ROI. Share your business design with the solution provider (or even better, ask them to help you create one) and watch out for those who dismiss it and want to get into the technical details too quickly. That is the trap to avoid in any technology implementation and the reason why so many projects fail. Use the business design to guide your selection of solution providers. As they start giving you information about how their solutions can address your goals and requirements, you can start using that to draw the technical design, detailing how things will get accomplished.

7. Kick Off the Technical Design

Many such projects start off with this step. However, until a comprehensive business design is completed, determining the technology solution is much like reading a book of fiction. A full technical design has its own seven steps, and the finished document is the roadmap for a successful implementation.

The Time to Start Is Now

Technology implementations take time and a lot of effort, especially if they involve changing the way people do things. As a result, CRM, ERP, and SCM systems and similar such tools are among the most costly and incur high failure rates due to exactly this problem: people! Involving all stakeholders while developing the business design and then the technical design will only help gain necessary support for the technological change that is inevitable.

 

Skipping the business design and diving into the implementation directly only leads to familiar pitfalls:

 

·        Resistance from users on changing the way they usually do things

·        System-integration issues

·        Short-term focus, sacrificing long-term viability

·        Limited, undefined, and misunderstood scope

·        Missed deadlines

 

Proper planning is the safest method to ensure expected outcomes are achieved for the users, managers, and people deploying the solution. Only then can the right technologies be selected and implemented optimally.

 

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: