Spreadsheet Reporting – No Room in Your Company in an Age of Business Intelligence

It doesn’t take a genius to understand why spreadsheet reporting still pervades the enterprise despite the rise of a complex but highly effective IT solution known to big shot CIOs as Business Intelligence or BI.

If you’re still in the dark as to what BI is, don’t worry because we?ll enlighten you shortly.

Business decisions from disparate data sources

In the meantime, let’s talk about how you make business decisions. If you’re a top executive, then you make decisions based largely on reports submitted to you by your managers, department heads, and so on. They in turn obtain information from different sources, like the company ERP and CRM as well as other external sources (e.g. market surveys).

Now, before their reports ever reach your desk, a lot of data is extracted, shared, filtered, analysed, consolidated, and summarised so that they become actionable information. In all these activities, one software tool gets to take part in most of the action – the spreadsheet.

The problem with spreadsheet reporting

The problem with spreadsheets is that they have very poor built-in controls. Thus, they are susceptible to human errors and are vulnerable to fraud. What’s more, collecting data and manually consolidating them into spreadsheets can be very laborious and time consuming.

If you don’t get accurate, reliable information, your judgement will be fuzzy and your business decisions compromised. In addition, if you don’t receive the information you need on time, your business will constantly be at risk of breaching critical thresholds, which may even force it to spin out of control.

Business Intelligence – actionable information on time

This is mainly the reason why large companies implement Business Intelligence systems. BI systems are equipped with built-in features like reports, dashboards, and alerts.

Reports consolidate data and present them in a consistent format composed of intuitive text, graphs, and charts. The main purpose of having a consistent format is so that you will know what kind of information to expect and how the information is arranged. That way, you don’t waste time searching or making heads or tails out of the data in front of you.

Dashboards, on the other hand, present information through visual representations composed of graphs and gauges that are aimed at tracking your business metrics and goals. The main function of dashboards is to feed you with actionable information at a glance.

Finally, alerts keep you informed when certain conditions are met or critical thresholds are breached. Because their main purpose is to prompt you at the soonest possible time wherever you are, a typical alert can come in the form of an SMS message or an email.

As you can see, all three features are designed to get you making well-informed decisions as quickly as possible.

The problem with Business Intelligence and the alternative solution

The usual problem with full BI systems is that they can be very costly. Hence, if your organisation does end up implementing one, chances are, not everyone under you will be able to access it. As a result, some departments will be forced to go back to using spreadsheets.

If your company cannot afford a full BI system, then that probably means you don’t need one. What you need is a more affordable alternative. There are actually Software as a Service (SaaS) Business Intelligence solutions that may not be as comprehensive as a full BI system, but which may suffice for small and mid-sized businesses.

The disadvantages of spreadsheets are more damaging than you could have ever expected. Be free of it now.

 

More Spreadsheet Blogs

 

Spreadsheet Risks in Banks

 

Top 10 Disadvantages of Spreadsheets

 

Disadvantages of Spreadsheets – obstacles to compliance in the Healthcare Industry

 

How Internal Auditors can win the War against Spreadsheet Fraud

 

Spreadsheet Reporting – No Room in your company in an age of Business Intelligence

 

Still looking for a Way to Consolidate Excel Spreadsheets?

 

Disadvantages of Spreadsheets

 

Spreadsheet woes – ill equipped for an Agile Business Environment

 

Spreadsheet Fraud

 

Spreadsheet Woes – Limited features for easy adoption of a control framework

 

Spreadsheet woes – Burden in SOX Compliance and other Regulations

 

Spreadsheet Risk Issues

 

Server Application Solutions – Don’t let Spreadsheets hold your Business back

 

Why Spreadsheets can send the pillars of Solvency II crashing down

?

Advert-Book-UK

amazon.co.uk

?

Advert-Book-USA

amazon.com

 

Check our similar posts

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.

 

Can you do away with the Project Initiation Meeting?

Project initiation meetings are often skipped to fast-track projects. Once a sponsor is found, organisations go straight to project planning and execution. But based on our own experience, holding a project initiation meeting can actually eliminate many issues that may crop up in the future and hence may speed things up instead in the long run.

It is in the project initiation meeting where your project objectives and scope are clarified and all stakeholders are brought to the same page. Project sponsors and stakeholders will have to know in a nutshell what is needed from them, what the possible risks are, what different resources are required, and so on. So that, when it’s time to proceed to the next phase, everyone is already in-sync.

So what are taken up in such a meeting? Perhaps an actual example can help. Sometime in the past, we set out to work on an eCommerce website project. After conducting the project initiation meeting, these were some of the things we were able to accomplish:

  • Identified deliverables e.g. site design, interface to payment system, etc.
  • Come up with the project phases
  • Agreed what should be in and out of scope
  • Defined the acceptance test criteria
  • Identified possible risks
  • Identified the possible training and documentation work needed
  • Established whether any analysis was required, e.g. as with regards to payment interfaces
  • Formulated disaster recovery plans
  • Defined roles and responsibilities
  • Drafted timelines and due dates

Aren’t these covered in project planning? If the project is a big one, the answer is no. In a large project, project planning is a much more exhaustive activity. In a project initiation meeting, only the basic framework is defined.

Some questions may still remain unanswered after a project initiation meeting, but at least you already know what answers you need to look for. In the example we gave earlier, we left the meeting knowing that we needed:

  • a list of all necessary hardware to estimate the costs
  • to identify possible dependencies we might have with third parties
  • to identify what software had to be bought and what skills we needed to hire

When it was time to proceed to project planning, everyone involved already knew what direction we were taking. In effect, by not skipping the project initiation meeting, we were able to avoid many potential obstacles.

Energy efficiency demystified

Energy bills are all about Energy efficiency but energy efficiency management is not all about bills. Energy efficiency means reducing carbon emissions, lowering energy costs and improving the quality of life. Energy efficiency is therefore about conservation of energy in a broader perspective; in fact energy efficiency is almost becoming a moral obligation.

Through adoption of appropriate energy efficiency measures, companies can significantly bring down the overhead costs making hundreds of dollars in savings. Energy efficiency is also synonymous with a better quality of life. Taking appropriate measures to ensure proper insulation protects your premises against extreme weather conditions leading to more productivity and an improvement in the bottom line.

Improved energy efficiency means a smaller amount of carbon emissions, less pollution and a better environment.

It is now easier than ever to visually identify where your facility is wasting energy, how much energy is being wasted while tracking the progress made in reducing energy consumption by turning that detailed, raw energy-consumption data into useful charts and figures.

Having visibility of your Energy usage gives you knowledge of what power you are consuming. This helps you change energy usage behaviours and this can have significant savings and reduction in your electricity bills. Real-time electricity consumption tracking is enough prodding for you to be on the lookout for inefficient energy consumption unit’s e.g.? Heating and cooling equipment, ducts insulation of your premises or a failure of one of these components to perform as intended. Pin-pointing the problem areas is not a walk in the park but fixing it can make your building more energy-efficient and comfortable.

A wide range of solutions are now available for charting and analysing energy consumption that helps energy managers, facilities managers, energy consultants and building-services engineers. These will not only offer advice but will enable you provide tailor made solutions for your organisation by assisting you in developing a sustainable energy strategy. Our energy monitoring software is one example.?

Ready to work with Denizon?

Contact Us Today