Skip to main content

HOAX - "Industry Best Practices"

I have seen a few major software vendors in the Business Process Management(BPM/BPA) domain demanding their customers to get rid of their processes and align the business with a general practice. The popular slogan they use to alienate this idea in your mind is

"Industry Best Practices"

Do we really need to be in what they called "industry's best practices" ?? What actually are the industry's best practices??

This is my little two cents about it........

Most of the time it's the uniqueness of the processes which makes the business a success. Hence you often find a well-defined set of processes behind every successful business.

In IT, this is a key principle to understand as continuous improvement and continuous delivery play crucial roles in the novel day IT world. Only a successful process pipeline can ensure your survival in the industry.

This processing pipeline you build in your organization should match your business modal. In that case, that pipeline can be a general one or a custom-made one that is unique to your organization.

For an instance, if you are running a typical software development company, you can use existing process pipelines as it is. But if you run a tech support company that provides support to a unique market like Oil & Gas, more often you should have your own ways of delivery other than the things mentioned in the book.

If your business is running in a common domain such as software engineering, your practices should be aligned with the competitors + you should have something unique to be on the top to get more on your plate. In supporting this type of modal, the best recommendation is to go with a popular tool stack to cover that common part to match your competitors and then select or implement a new tool to manage the unique part of your business.

If you are in a focussing a market niche (i.e Oil & Gas mentioned in the example), you should have unique processes to cater to those specific requirements. In such cases, you should explore and stack your processes to match the requirement and later need to decide on a tool stack to match your requirement. The only best practice you should care for should be "Flexibility" as being in a niche requires it a lot to match with the changes of the parent business modal.

Personally, I haven't seen BPM software that can make a successful business modal nor do I believe that can be done. But a successfully selected software or a set of software can ensure the success of your business modal.

So anyone who wishes to digitalize their business processes should be mindful when a vendor asks you to be aligned with "Industry Best Practises". First, understand what makes your business a success. If it's a set of unique processes, just find a tool or set of tools that cater to it. Not vice versa.

Comments

Popular posts from this blog

Limitations of If Else Statements in ServiceNow Flow Designer

The ServiceNow Flow Designer is a powerful tool for automating workflows and processes. However, the If Else statement within the Flow Designer has certain limitations that users must be aware of, particularly when it comes to complex conditions, nesting, performance, debugging, user interface, maintenance, and scalability. Complex Conditions A significant limitation of the If Else statement in ServiceNow Flow Designer is its handling of complex logical operators. The Flow Designer supports basic conditions, but it may not handle operators like AND, OR, and NOT as intuitively as some other platforms. Combining multiple conditions can sometimes become cumbersome, making it challenging to implement sophisticated business logic effectively. Nested If Else Statements While it is possible to nest If Else statements within the Flow Designer, there is a practical limit to how deeply they can be nested. Excessive nesting can lead to a cluttered and hard-to-read flow, making it difficult to man...

Strategically Positioning ServiceNow in Your Organizational Roadmap

Here’s how you can strategically position ServiceNow in your organizational roadmap. 1. Assessment and Alignment with Business Goals Step 1: Comprehensive Needs Assessment Begin by conducting a thorough assessment of your organization’s current processes, pain points, and future aspirations. Identify the areas where automation and improved workflows can have the most impact. Step 2: Align with Business Objectives Align these findings with your overarching business goals. Whether it’s improving customer satisfaction, enhancing employee productivity, or ensuring better compliance and risk management, understanding how ServiceNow can support these objectives is crucial. 2. Building a Cross-Functional Team Step 1: Engage Stakeholders Form a cross-functional team that includes representatives from IT, HR, finance, and other critical departments. Their insights will be invaluable in understanding the unique needs and challenges of each department. Step 2: Define Roles and Responsibilities Cl...

ServiceNow, ITIL and Agile - A different symphony

As a 9+ experienced Solution Architect who is mainly focusing on software system automation in ITSM Domain, I had the invaluable opportunity of being a part of a few successful business transitioning projects. With that experience on hand, I'm writing this article to share the challenges you can expect during this kind of transition. Agile Since we are in a rapidly changing business world which directly depends on IT, IT organizations play major roles in every business. Bigger the company, the responsibility of the IT company getting bigger and bigger day by day. Things get much more complicated when an IT organization supports IT businesses like Software development firms or Infrastructure services providers. Therefore a better process of managing delivery activities is required for such an IT company.  Many years ago, When Agile invaded the tech market, businesses eagerly looked forward to restructuring their IT organizations according to those practices.  Agile is a pr...