Six Sigma

Six Sigma has received much attention worldwide as a management strategy that is said to have brought about huge improvements and financial gains for such big-name companies as Allied Signal, General Electric (GE) and Motorola.

If you want to give your business the chance to attain the same resounding success, Six Sigma could be the method that will steer you towards that direction.

What is Six Sigma?

So what really is it? Six Sigma is a business management tool that was developed using the most effective quality improvement techniques from the last six decades. Basing its approach on discipline, verifiable data, and statistical calculations, Six Sigma aims to identify the causes of defects and eliminate them, thereby resulting in near-perfect products that meet or exceed customer’s satisfaction.

The core concept behind the Six Sigma method is that if an organisation can quantify the number of “defects” there are in a particular process, improvement activities can be implemented to eliminate them, and get as close to a “zero defects” scenario as possible. Defect here is defined as any process output that fails to meet customer specifications.

Six Sigma is also unique from other programs in that it calls for the creation of a special infrastructure of people within the organisation (“Champions“, “Black Belts“, “Green Belts“) who are to be expert in the methods.

Six Sigma Methodologies

When implementing Six Sigma projects, two methodologies are often employed. Although each method uses five phases each, these two are distinguished from each other using 5-letter acronyms and their specific uses.

DMAIC ? is the project methodology used to improve processes and maximise productivity of current business practices. The 5 letters stand for:

  • D ? Define (the problem)
  • M ? Measure (the main factors of the existing process)
  • A ??Analyse?(the information gathered to deter mine the causes of defects)
  • I ? Improve (the current process based on the analysis)
  • C ? Control (all succeeding processes so as to minimise additional defects)

DMADV – is the method most suitable if your business is looking to create new products or designs. The acronym stands for:

  • D ? Define (product goals as the consumer market demands)
  • M ? Measure (and identify product capabilities and risks)
  • A ??Analyse?(to create the best possible design)
  • D ? Design (the product or process details)
  • V ? Verify (the design)

How does Six Sigma differ from other quality programs?

If you think that Six Sigma is just another one of those business strategies that produce more hype than actual results, think again. Six Sigma uses three key concepts that sets it apart from other business management methods.

  • It is strictly a data-driven approach, where assumptions and guesswork do not figure in the decision making.
  • It focuses on achieving quantifiable financial results ? the bottom line ($) ? as much as giving emphasis on customer satisfaction.
  • It requires strong management leadership, while at the same time creating a role for every individual in the organisation.

Is Six Sigma right for your business?

While many other organisations such as Sony, Nokia, American Express, Xerox, Boeing, Kodak, Sun Micro-systems and many other blue chip companies have followed suit in adopting Six Sigma, the truth is, any company — whether you have a large manufacturing corporation, or a small business specialising in customer service.

Certainly, there is a lot more to Six Sigma than what you can probably absorb in one sitting or reading.

With our wide range of business management consultancy services, we can help you understand the Six Sigma method in the context of your business. We can also help you establish your improvement goals, set up your program, and train your own team of “champions” who can lead in implementing your Six Sigma goals.

Find out more about our Quality Assurance services in the following pages:

Check our similar posts

Finding the Best Structure for Your Enterprise Development Team

An enterprise development team is a small group of dedicated specialists. They may focus on a new business project such as an IoT solution. Members of microteams cooperate with ideas while functioning semi-independently. These self-managing specialists are scarce in the job market. Thus, they are a relatively expensive resource and we must optimise their role.

Organisation?Size and Enterprise Development Team Structure

Organisation structure depends on the size of the business and the industry in which it functions. An enterprise development team for a micro business may be a few freelancers burning candles at both ends. While a large corporate may have a herd of full-timers with their own building. Most IoT solutions are born out of the efforts of microteams.

In this regard, Bill Gates and Mark Zuckerberg blazed the trail with Microsoft and Facebook. They were both college students at the time, and both abandoned their business studies to follow their dreams. There is a strong case for liberating developers from top-down structures, and keeping management and initiative at arm?s length.

The Case for Separating Microteams from the?Organisation

Microsoft Corporation went on to become a massive corporate, with 114,000 employees, and its founder Bill Gates arguably one of the richest people in the world. Yet even it admits there are limitations to size. In Chapter 2 of its Visual Studio 6.0 program it says,

‘today’s component-based enterprise applications are different from traditional business applications in many ways. To build them successfully, you need not only new programming tools and architectures, but also new development and project management strategies.?

Microsoft goes on to confirm that traditional, top-down structures are inappropriate for component-based systems such as IoT solutions. We have moved on from ?monolithic, self-contained, standalone systems,? it says, ?where these worked relatively well.?

Microsoft’s model for enterprise development teams envisages individual members dedicated to one or more specific roles as follows:

  • Product Manager ? owns the vision statement and communicates progress
  • Program Manager ? owns the application specification and coordinates
  • Developer ? delivers a functional, fully-complying solution to specification
  • Quality Assurer ? verifies that the design complies with the specification
  • User Educator ? develops and publishes online and printed documentation
  • Logistics Planner ? ensures smooth rollout and deployment of the solution

Three Broad Structures for Microteams working on IoT Solutions

The organisation structure of an enterprise development team should also mirror the size of the business, and the industry in which it functions. While a large one may manage small microteams of employee specialists successfully, it will have to ring-fence them to preserve them from bureaucratic influence. A medium-size organisation may call in a ?big six? consultancy on a project basis. However, an independently sourced micro-team is the solution for a small business with say up to 100 employees.

The Case for Freelancing Individuals versus Functional Microteams

While it may be doable to source a virtual enterprise development team on a contracting portal, a fair amount of management input may be necessary before they weld into a well-oiled team. Remember, members of a micro-team must cooperate with ideas while functioning semi-independently. The spirit of cooperation takes time to incubate, and then grow.

This is the argument, briefly, for outsourcing your IoT project, and bringing in a professional, fully integrated micro-team to do the job quickly, and effectively. We can lay on whatever combination you require of project managers, program managers, developers, quality assurers, user educators, and logistic planners. We will manage the micro-team, the process, and the success of the project on your behalf while you get on running your business, which is what you do best.

Contact Us

  • (+353)(0)1-443-3807 – IRL
  • (+44)(0)20-7193-9751 – UK
What Is Technical Debt? A Complete Guide

You buy the latest iPhone on credit. Turn to fast car loan services to get yourself those wheels you’ve been eyeing for a while. Take out a mortgage to realise your dream of being a homeowner. Regardless of the motive, the common denominator is going into financial debt to achieve something today, and pay it off in future, with interest. The final cost will be higher than the loan value that you took out in the first place. However, debt is not limited to the financial world.

Technical Debt Definition

Technical debt – which is also referred to as code debt, design debt or tech debt – is the result of the development team taking shortcuts in the code to release a product today, which will need to be fixed later on. The quality of the code takes a backseat to issues like market forces, such as when there’s pressure to get a product out there to beat a deadline, front-run the competition, or even calm jittery consumers. Creating perfect code would take time, so the team opts for a compromised version, which they will come back later to resolve. It’s basically using a speedy temporary fix instead of waiting for a more comprehensive solution whose development would be slower.

How rampant is it? 25% of the development time in large software organisations is actually spent dealing with tech debt, according to a multiple case study of 15 organizations. “Large” here means organizations with over 250 employees. It is estimated that global technical debt will cost companies $4 trillion by 2024.

Is there interest on technical debt?

When you take out a mortgage or service a car loan, the longer that it takes to clear it the higher the interest will be. A similar case applies to technical debt. In the rush to release the software, it comes with problems like bugs in the code, incompatibility with some applications that would need it, absent documentation, and other issues that pop up over time. This will affect the usability of the product, slow down operations – and even grind systems to a halt, costing your business. Here’s the catch: just like the financial loan, the longer that one takes before resolving the issues with rushed software, the greater the problems will pile up, and more it will take to rectify and implement changes. This additional rework that will be required in future is the interest on the technical debt.

Reasons For Getting Into Technical Debt

In the financial world, there are good and bad reasons for getting into debt. Taking a loan to boost your business cashflow or buy that piece of land where you will build your home – these are understandable. Buying an expensive umbrella on credit because ‘it will go with your outfit‘ won’t win you an award for prudent financial management. This also applies to technical debt.

There are situations where product delivery takes precedence over having completely clean code, such as for start-ups that need their operations to keep running for the brand to remain relevant, a fintech app that consumers rely on daily, or situations where user feedback is needed for modifications to be made to the software early. On the other hand, incurring technical debt because the design team chooses to focus on other products that are more interesting, thus neglecting the software and only releasing a “just-usable” version will be a bad reason.

Some of the common reasons for technical debt include:

  • Inadequate project definition at the start – Where failing to accurately define product requirements up-front leads to software development that will need to be reworked later
  • Business pressure – Here the business is under pressure to release a product, such as an app or upgrade quickly before the required changes to the code are completed.
  • Lacking a test suite – Without the environment to exhaustively check for bugs and apply fixes before the public release of a product, more resources will be required later to resolve them as they arise.
  • Poor collaboration – From inadequate communication amongst the different product development teams and across the business hierarchy, to junior developers not being mentored properly, these will contribute to technical debt with the products that are released.
  • Lack of documentation – Have you launched code without its supporting documentation? This is a debt that will need to be fulfilled.
  • Parallel development – This is seen when working on different sections of a product in isolation which will, later on, need to be merged into a single source. The greater the extent of modification on an individual branch – especially when it affects its compatibility with the rest of the code, the higher the technical debt.
  • Skipping industrial standards – If you fail to adhere to industry-standard features and technologies when developing the product, there will be technical debt because you will eventually need to rework the product to align with them for it to continue being relevant.
  • Last-minute product changes – Incorporating changes that hadn’t been planned for just before its release will affect the future development of the product due to the checks, documentation and modifications that will be required later on

Types of Technical Debt

There are various types of technical debt, and this will largely depend on how you look at it.

  • Intentional technical debt – which is the debt that is consciously taken on as a strategy in the business operations.
  • Unintentional technical debt – where the debt is non-strategic, usually the consequences of a poor job being done.

This is further expounded in the Technical Debt Quadrant” put forth by Martin Fowler, which attempts to categorise it based on the context and intent:

Technical Debt Quadrant

Source: MartinFowler.com

Final thoughts

Technical debt is common, and not inherently bad. Just like financial debt, it will depend on the purpose that it has been taken up, and plans to clear it. Start-ups battling with pressure to launch their products and get ahead, software companies that have cut-throat competition to deliver fast – development teams usually find themselves having to take on technical debt instead of waiting to launch the products later. In fact, nearly all of the software products in use today have some sort of technical debt.

But no one likes being in debt. Actually, technical staff often find themselves clashing with business executives as they try to emphasise the implications involved when pushing for product launch before the code is completely ready. From a business perspective, it’s all about weighing the trade-offs, when factoring in aspects such as the aspects market situation, competition and consumer needs. So, is technical debt good or bad? It will depend on the context. Look at it this way: just like financial debt, it is not a problem as long as it is manageable. When you exceed your limits and allow the debt to spiral out of control, it can grind your operations to a halt, with the ripple effects cascading through your business.

 

What is Servitisation?

In the current generation, innovation has transformed industries, businesses, economies, and livelihoods. Those who’ve accepted to embrace the changes have prospered and remained afloat and relevant in their respective industries.?

However, failure to embrace change has seen companies like Blockbuster pushed out of business by more innovative and technology-oriented companies like Netflix.?

What does this tell you?

That the only way to stay in business, despite the many challenges your business could be facing, is to remain alert to the dynamic demands of customers, many of which are dictated by technological advancements.?

So, if you’re a manufacturer and you’re keen on diving deeper into technology to stay on top of the game and beat your competition, you must also be expectant of the fast-approaching servitisation-centred economy. Companies like Rolls Royce that have already embraced servitisation are making great gains in their areas of expertise.?

What is Servitisation?

Servitisation can be defined as the transformation of a manufacturing firm from the mere offering of products to the market to providing innovative and invaluable services alongside their products. By so doing, the sale becomes an ongoing engagement and not a one-off event. Cranfield University professors call it “the innovation of an organisation’s capabilities and processes to better create mutual value through a shift from selling a product to selling product-service systems.”?

As foreign as it may seem for some professionals, servitisation has been a need that, though not embraced, its demand remains evident. Nonetheless, firms have hesitated to implement it. Shifting from manufacturing products only to incorporating product-centric services alongside the products is not a walk in the park. It boils down to completely changing the company’s entire structure and processes.

All the same, change is never comfortable, and that’s why it’s always best to focus on the positive for motivation.

Servitisation Case Study

Some manufacturing firms have already embraced servitisation, and they’re reaping big from it. They’ve understood the benefits of offering more value to customers at less cost. What Rolls Royce is doing currently with its “power-by-the-hour” program is a good example of servitisation.

Instead of selling Aero Engines and letting customers take charge of maintenance and uptime, Rolls-Royce now offers a full package that includes a product and relevant services.?

Essentially, what the company is creating is an intimate and long-term relationship with its customers.

The total care package by Rolls Royce means it’s essentially renting out its engines to customers and monitoring data for potential maintenance needs. The plan guarantees that maintenance is only done when necessary and avoidable damage detected in good time. As a result, there is a clear reduction in the overall cost.

Initially, Rolls Royce would make money by basically selling and repairing engines. That meant that the worse the engines, the more repairs required and the more the money the company would make.?

However, things changed when the company realised there is no demand for a product that’s constantly in the repair shop. That prompted Rolls Royce to embrace servitisation.

Servitisation aligns the interests of the customer and those of the manufacturer to ensure everyone benefits. Rolls Royce has been offering this package to airlines since 2010, and the company has seen significant returns as a result.

Benefits

There are several benefits of incorporating servitisation into your manufacturing firm. Below are three of the strongest benefits

  • Financial Stability– Servitisation establishes a more secure revenue stream because of the long term connection between manufacturer and customer. This also translates to loyal customers, meaning more profit.
  • Strong Customer Retention Rate– Being more experienced about the equipment and the constant tracking and monitoring that comes with servitisation; manufacturers are realising that they can keep more customers.
  • Selling a Solution And a Product– Today customers are not just looking to buy a product, instead, they want both the product and the solution to their problem. Meaning you make more money for the product you manufacture and the service you offer to your customers.

Implementation of Servitisation in the Industry

To effectively implement servitisation, there must be an effective two-way flow of information and data in the supply chain. Meaning you may require software like FieldElite for scalable condition monitoring of performance. With FieldElite, for example, servitisation is made easier for you because it enables you to monitor the performance of your assets remotely.

Maintenance and monitoring of assets were traditionally very expensive and time-consuming until the arrival of intelligent software that makes work easier and cost-effective for manufacturers. FieldElite uses advanced learning algorithms to remotely automate the entire process, allowing you to detect, in real-time, the performance and need for maintenance on your asset.

Required Organisational Changes

A few important steps include;

Companies that invest in continuous training and development always have a more competitive edge than their counterparts. Meaning an important step towards servitisation is training the workforce. This is important, considering that the company structure, focus, and process will have to change.

Set up a team that is focused on the challenge, change, and creation. With this, you can easily adjust to industry changes. The team should always work on knowing what should be adjusted and when it should be.?

In the shift to servitisation, adopting a comprehensive service technology is an important step. Such service technology software includes FieldElite. This technology will ensure that you’re able to monitor your product in real-time, meaning you can maintain good performance for as long as possible.

Because servitisation essentially focuses on the customer, take time to study customer behaviour. Knowing what your customers need and want will help you remain relevant in the industry.

Conclusion

As the demand for more benefits and long-lasting relationships with dealers grow, so is the need for manufacturers to adjust. Hence more and more manufacturing companies are leaning towards embracing servitisation as a solution to the growing demand.?

In turn, manufacturers who’re attaching service contracts to their product sales are making more than those who remain stuck in the traditional approach to sales.?

Essentially, servitisation will ensure that, as a manufacturer, you remain relevant to your customers now and in years to come. This is a much better arrangement in terms of saving costs and making more returns. Remember to be successful, you have to be flexible enough to change with demand.

Ready to work with Denizon?

Contact Us Today