What causes technical debt – and how can you solve it? Pritesh Pattni What causes technical debt – and how can you solve it?  Technical debt is present – to a lesser or greater degree – in every company. The term refers to the technical problems that arise from short-term or cost-based decisions that affect the quality of the technology solutions within the business.   There are several key causes of technical debt. Some of these are easy to identify, while others are only discovered when they create other problems in the business. In some businesses, new leadership – such as a change of CIO or CTO – can result in an audit to uncover technical debt. This helps the business understand where the potential weaknesses may be, and put a plan in place to strengthen the technology stack across the organisation.  The central causes of technical debt  Usually, technical debt is incurred by taking short cuts. This often happens for a variety of reasons, including:  Time pressure – development teams are under pressure to meet tight deadlines in order to get a product to market, or release a new feature internally. This pressure often means that testing isn’t thorough enough, or code isn’t properly written. While the application itself might work in the short term, there will be issues that are difficult to fix – such as adding new features or finding bugs in the system – and can cause significant problems for the business in the long term.  Poor design thinking – developing a new piece of technology takes time, thought and a clear strategy. Where that thinking hasn’t been done, the resulting application can lack scalability, usability and have other performance issues. There are several reasons why this might happen – design might be outsourced with a poor brief, for example, or an internal team may not have the strategic design experience to manage this important stage of the development process.  Inadequate documentation – while it might seem less important than the technology, documentation is vital for ensuring that people can understand the design and development strategy and the way the application has been coded. Failing to do this means that future team members are effectively working blind. Any changes they make could undermine the original code, resulting in performance problems. This knowledge gap is a common form of technical debt, and it can have a  substantial impact.  Limited testing – testing is a critical part of the development project. It’s not just about making sure the end user can use the application properly – it’s about checking the application for bugs and for maintenance issues, so that there is complete confidence before release. Where testing is rushed or inadequate, you cannot be sure that the application is fit for purpose. Potential problems can be missed. Fixing these, in the long term, results in time and cost implications.  Project brief changes – it’s not unusual for new application requirements to change. It’s all part of the process, with project owners looking for additional features or functionality. The way these updates are managed, however, has a serious impact on the potential for technical debt. Unless a clear system is in place to raise, discuss, design and test new features, the project can become confused, with several people ‘owning’ coding areas and poor communication resulting in functional problems.  Lack of collaboration – projects need to be regularly reviewed within the team  – and beyond – for them to be successful. Daily meetings, along with using collaborative online project tools, help teams to keep track of progress and responsibilities. This avoids problems caused by working in silos, which can result in things being missed, or duplicated.  Underskilled development teams – to keep costs down, organisations may use inexperienced developers. While they may have the appropriate coding skills, a lack of project experience can result in problems down the line. Saving money in this way will result in far more cost in the future.  Legacy technology – one of the most common causes of technical debt is the technology that’s already in the business. Platforms or solutions that are no longer supported by the original manufacturer, or that was developed in-house but never updated, will create inefficiencies. They may also be unable to work alongside newer technologies, restricting the value of investment in those new solutions.  Identifying technical debt  It’s all very well to know what the causes of technical debt are – but if you can’t identify it in your organisation, you will still struggle to solve the issues it creates. There are some key signs that you might have technical debt, including:  Development speed is slower than expected.  There are frequent bugs and recurring usability problems.  Systems go down more often.  Developers find that code is difficult to modify or extend.  New team members don’t have access to reliable documentation about the application.  Testing records are incomplete.  Easy updates are slow to release.  Maintenance takes more time and costs more money.  You can’t scale the application when you need to.  Manufacturers have stopped updating or supporting existing technology.  When you discover technical debt, you need to do something about it. Failure to pick this up can negatively impact your business. Investing in solutions to resolve technical problems – and make sure they are fit for the future – is an investment in your bottom line.  You might want to think about:  Severity – how much is the technical debt impacting your team’s ability to develop and release features or maintain the system?  Risk – is the debt leading to potential security vulnerabilities, system instability, or performance issues?  Cost – how much time and effort is required to address the debt compared to the time spent working around it?  Visibility – is the technical debt causing noticeable issues for customers? Have you had complaints?  This will help you to prioritise the technical debt that needs addressing first, and start to put a plan together. At this point, it’s worth talking

The synergy of design, code, and development Pritesh Pattni The synergy of design, code, and development Like all disciplines, digital development works best when all the various elements are used collaboratively, and where new approaches are created based on the input of experts in each area. Depending on the type of development, new technologies can be expensive and time-consuming to create, and this is only exacerbated when some parties are consulted late in the day, or assumptions are made. That’s why uniting design, code and development is seen as the best approach for a successful technology project. In this article, we look at why this synergy is important. What is design? For technology projects, design is the process of creating visual and functional concepts that  are focused on delivering a great user experience. This often covers a range of design expertise, including graphic design, user interface design and user experience design. Working together, these designers use their experience and understanding of aesthetics, usability and psychology to build a visual approach that attracts users while accurately representing the end brand. What is code? Code, in the context of software development, refers to the instructions written in a programming language to define the behaviour and functionality of a system or application. It covers both frontend code, which is focused on the user interface and interaction, and backend code, which manages data storage, processing, and communication with servers and other systems. Code is used to translate design concepts into executable software, employing algorithms, data structures, and software architectures to bring ideas to life. There are usually two approaches to coding: traditional hand coding and low code. Hand-coding is where every element of the code is written by a professional developer and is often used on complex projects. Low code is an approach that uses a drag-and-drop interface to create certain elements of a project, reducing time and cost, and ensuring reliability. The type of coding used on a technology project will be determined by the type of project, timescales and budget. What is development? Development is the term given to the broader process of creating, deploying, and maintaining software solutions. It is often used just to describe the technical aspects of coding, but it also involves the strategic planning and management required to deliver successful products. Ideally, development teams will collaborate across disciplines, including design, engineering, quality assurance, and project management, to build software solutions that meet user needs and business objectives. Why collaboration matters To run a successful technology project, all these elements must come together. Design, with its focus on aesthetics, usability, and user experience, lays the foundation for intuitive interfaces and engaging interactions. Whether it’s crafting visually compelling layouts or mapping out user journeys, design serves as the initial touchpoint, drawing users into the product. Design – both for aesthetics and for usability – is a critical part of the process, giving coders the direction they need to create a workable solution. But ‘design’ and ‘code’ shouldn’t work in a vacuum. Of course, coders could wait until the design process is complete, and then take over, but the project will be far more efficient when designers and coders work together from the very beginning. This is where creativity and technical understanding can work together to create not just a functional and high-performing solution, but to manage the project in the best way from end to end. Designers provide developers with the blueprint for innovation, while developers empower designers with the tools to realize their vision. This synergy fosters a culture of creativity and refinement, where ideas evolve organically through continuous feedback and open conversations. Beyond individual projects Of course, collaboration helps individual projects to succeed. Sometimes, all the elements of design, code and development are based within internal teams, which makes this teamwork easier. On other projects, the project development team may be internal, while the design and coding is outsourced. In cases like this, it’s essential to bring teams together regularly to establish and build good relationships to help the project run smoothly. Beyond individual projects, this focus on collaboration is being encouraged across the technology industry. Leaders understand both the commercial benefits of working more collaboratively, and the fact that this approach delivers better outcomes for users. Agile methodologies, using iterative development and cross-functional teams, has blurred the lines between design and code, removing the risk of siloed thinking, and producing more efficient and effective results. Why low code is a good collaborative option In the context of uniting design, code, and development, low-code platforms offer several advantages over hand-coding approaches. First, they enable rapid prototyping and iterative development cycles. This helps to bring technologies to market faster, and results in more reliable end applications. Low code also streamlines the development process by eliminating complex technical details. This means the development team can focus on high-level functionality and business logic, rather than getting tied up with every small detail. By reducing the amount of hand coding required, using low code can increase productivity and efficiency, and drives faster, more cost-effective delivery. At ISB Global, we are a proud OutSystems partner. OutSystems is regularly named as a platform of choice for collaborative teams. It’s an open platform that accelerates development without compromising quality, and leaves room for easier adaptation and scalability. We use OutSystems low code both for our own market-leading application, Waste and Recycling One, and for the development projects we work on for clients. Contact us to find out more about how low code and collaborative working could help your business to build stronger technologies. Recommended Posts​ What is the true cost of technical debt? What is the true cost of technical debt? Pritesh Pattni What’s the true cost of technical debt?  Technical debt comes in a variety of guises, and occurs for many different reasons. However your tech… Read More Is your software future-proofed? Is your software future-proofed? Pritesh Pattni Is your software future-proofed? As we move rapidly towards full digital transformation, businesses are relying

What is the true cost of technical debt? Pritesh Pattni What’s the true cost of technical debt?  Technical debt comes in a variety of guises, and occurs for many different reasons. However your tech debt is accrued, it has a future cost for your business – both in terms of the operational impact on your business, and the cost of getting your tech into a better position.  We’ve talked in other articles about the seven main types of technical debt. The reasons that software developers can create technical debt will vary – and they will be different for each type of debt. These include:  Prioritising speed over accuracy – sometimes, this is done in the knowledge that technical debt will occur. Developers and project leaders decide that it’s more important to release software quickly than to make sure it’s perfect. In some cases, there is a plan to manage software updates and releases to deal with that debt, but in others, teams simply take the hit without having a plan to improve quality.  Lack of clear communication or collaboration – this often happens when more than one organisation is working on the software. For example, part of the development work may have been outsourced, but without the details of requirements, testing or outcomes fully explained. But it can also happen internally, particularly with larger teams, and this can have serious consequences for customers and users.  Pressure to go to market – this can be particularly prevalent in traditional hand-coding projects, which often take longer because they require more people and use slower processes. Software is a highly competitive market, and success can be entirely down to getting your product to market ahead of the competition. But in the rush to get to market, project managers or senior leaders in the organisation may put developers under pressure to cut corners, reduce testing or remove features. The product gets to market first, but doesn’t have the quality it needs to achieve a market-leading position.  Learning ‘on the job’ – this can happen when developers are working with a new system, language or database. There is often a significant learning curve, and so things may be missed, or incorrectly coded. This will result in technical debt, but it also improves the capabilities of the development team and they will build the knowledge they need to improve the software in the future.  For organisations, getting into technical debt also happens for a variety of reasons. When you combine these with the software development technical debt issues, you can see that one can compound the other. Organisational technical debt can occur where:  Fast solutions, not best solutions – as organisations grow, they need more technology. Often, this technology is critical to the next stage of growth, so there isn’t the time to evaluate the options properly. This leads to solutions being implemented that solve the immediate problem, but are not scalable or adaptable.  Cost-cutting – any technology vendor will tell you that many organisations place the cost of a solution at the top of the priority list. So businesses will often end up with a solution that was cost-effective at the time of purchase, but becomes increasingly inefficient and ineffective as time goes on. That initial saving often turns into a long-term cost.  Legacy systems from business change – when organisations merge, or a smaller organisation is acquired, it can lead to issues with legacy systems. Although this is often taken into consideration operationally, businesses may not assess the full cost of the technical debt caused by opting for one system over another.  The true cost of technical debt will vary from company to company. But we’ve highlighted this example from a McKinsey report on technical debt because it illustrates just how quickly it can build, and the strategic cost it can have.  “A large B2B business faced an agonizing quandary: its leadership team was considering dozens of modernization initiatives that could bring a $2 billion margin expansion opportunity. But 70 percent of them depended on technology that would cost a staggering $400 million—much higher than expected. The reason for such a high price tag? Its tech stack had become massively complex after years of building quick workarounds and one-off solutions to favor speed over good design for the long term.”  What this shows is that organisations shouldn’t wait to assess their technical debt. They should start to look now at what is working and what isn’t, and find a low code development partner that can help them get back in the black.  Why low code? Because it transforms the way that developers work, producing more cost-effective, flexible and scalable applications that work with the organisation, not against it. At ISB Global, we are a proud OutSystems partner. OutSystems is a globally-leading low code platform that delivers secure, efficient and versatile software to meet any challenge. Just get in touch with us today to find out more. Recommended Posts​ The synergy of design, code, and development The synergy of design, code, and development Pritesh Pattni The synergy of design, code, and development Like all disciplines, digital development works best when all the various elements are used… Read More Is your software future-proofed? Is your software future-proofed? Pritesh Pattni Is your software future-proofed? As we move rapidly towards full digital transformation, businesses are relying on a raft of software solutions to help… Read More An evolutionary approach to software engineering An evolutionary approach to software engineering Pritesh Pattni Evolution. The gradual development of something to make it even better. It’s this approach that underpins the low code software… Read More Where next? I’m an OutSystems Customer looking for Applications to accelerate my journey → I’m an OutSystems customer looking for patterns & features to accelerate my journey → I’m an OutSystems Customer using SAP and looking for an advanced integration engine → I’m an OutSystems customer and I need additional development support for my team →

Is your software future-proofed? Pritesh Pattni Is your software future-proofed? As we move rapidly towards full digital transformation, businesses are relying on a raft of software solutions to help them manage their day-to-day operations, store critical data securely, and drive the strategies that promote growth and long-term success. Not all software is equal, though. Older systems are often slower to use, less easy to interrogate, don’t integrate with other systems and can even be at a stage where the software company no longer offers updates or support. Today’s software must be designed and developed with an eye to the future. Whether you are building a system in-house, or buying systems in from elsewhere, the scalability, flexibility and adaptability of the software system must be key considerations. In this article, we talk about why this is so important, and how taking a low code approach could deliver the future proofing you need. Software is changing In fact, this isn’t a recent occurrence. Like all fundamental technologies, software development is changing all the time. Developers live in a fast-paced and competitive environment, where users have certain expectations and demands, and businesses want more software for their money. This can pose problems for the hand-coding approach – the traditional method of software development where developers hand-write their code from scratch. That’s because this is a more time-consuming way to write software – and therefore more expensive. It can also be more prone to errors or bugs, simply because it relies entirely on human authoring and testing. This is why, over the past 20 years, we have seen the emergence of a low code approach. Low code development uses a visual drag-and-drop interface, using pre-designed elements to improve both the speed of development and its accuracy. The ability to use a dedicated platform also promotes better collaboration between developers and their clients – whether they are internal or external – and also allows software to be built that can be updated or scaled quickly and easily. How low code supports future proofing So, low code reduces development time, removes much of the error risk, and helps developers to build flexible software. This in itself supports future-proofing, and there are a number of benefits to this approach: Agile development – using low code platforms supports a more flexible development lifecycle, which allows developers and organisations to respond quickly and accurately to changes in business requirements, market demands or competitive features. The ability to be able to quickly design, test and deploy software applications to help businesses flex to maintain or improve market position. Scalable approach – rather than going through a cycle of constantly upgrading or changing software to meet the demands of a growing business, a low-code approach allows developers to expand the current application to meet new needs. This may be extending functionality to a new department, bringing on board a business that has been acquired, or simply upgrading the software to allow for a more efficient approach. Less technical debt – ‘technical debt’ is a term used to describe software that can no longer deliver what the organisation needs. This slows down productivity and can actively get in the way of growth. With a low code development solution, the code is simpler, the ability to change or adapt is greater and so technical debt declines. Better security – this is a core requirement for all today’s software. Organisations are at constant risk of attack and need to demonstrate that they have put the security of their systems and their data first. While some businesses just focus on security, others also have to demonstrate compliance with both government and regulatory requirements. So today’s development is not just about building a future-proofed user experience; it’s about ensuring the organisation is always meeting or exceeding its security and compliance requirements. Why we use OutSystems OutSystems is a pioneer of the low code approach, and has been developing its platform for the past 20 years. It’s built up a loyal following among professional developers, who can see the numerous benefits of using its intelligence to build software faster, while also retaining control over design and architecture. We are a proud OutSystems partner, using its low code technology to build our industry-leading platform, Waste and Recycling One. We also use OutSystems to build discrete applications for clients, giving them the high quality, future-proofed development they are looking for at a price they can afford. Recommended Posts​ An evolutionary approach to software engineering An evolutionary approach to software engineering Pritesh Pattni Evolution. The gradual development of something to make it even better. It’s this approach that underpins the low code software… Read More How to choose a low code platform partner How to choose a low code platform partner Pritesh Pattni If you have a technology project or digital transformation programme, you are probably considering a low code solution. Low code offers a range… Read More What is low code technology? And why should you consider it? What is low code technology? And why should you consider it? Pritesh Pattni The demand for new and upgraded technology isn’t going anywhere. The human race continues to adopt new technologies to… Read More Where next? I’m an OutSystems Customer looking for Applications to accelerate my journey → I’m an OutSystems customer looking for patterns & features to accelerate my journey → I’m an OutSystems Customer using SAP and looking for an advanced integration engine → I’m an OutSystems customer and I need additional development support for my team →

How to choose a low code platform partner Pritesh Pattni If you have a technology project or digital transformation programme, you are probably considering a low code solution. Low code offers a range of benefits when compared with traditional hand coding. These benefits include speed of development, cost-effectiveness and easier maintenance. If low code is the option you choose, you’ll need to find a partner to work with, and you’ll want to know as much as you can about which low code platform they use and why.  What is a low code platform? In recent years, the Low Code revolution has transformed the way applications, software and solutions are developed. The first thing to understand is that Low code development is platform based. The number of low code platforms on the market is increasing, with both well-known brand names and new entrants vying to offer the best solution for development teams. The most common low code platforms are: OutSystems Quickbase Airtable Appian Caspio In addition, well-known tech brands like Microsoft and Salesforce have developed their own low code platforms, and there are plenty of other suppliers out there. Like all technology platforms, this competition means that it can be quite tricky to decide which platform will be best for your needs. When you approach a potential development partner, they will have a set of questions for you, to help determine the scope of your project and so that they can tell you how they can design and build your software using low code. How to prepare to choose a low code platform partner In order to make the process as easy as possible, it’s best to be prepared for the questions your target suppliers might ask. This means you need to take a step back from ‘I need to hire a development team’ to think about questions like ‘What do we want the software to achieve?’ This consideration takes two forms: the practical things you need from the software, and the relationship and service you need from your supplier. So here are some things to think about: How to choose the right low code software for your business Are you replacing existing technology?  For example, a company may have a critical process that is currently managed via a complex Excel spreadsheet. Spreadsheets have their place, but they are not the best technology for many agile processes, so the company might want to introduce an app instead.  If you’re replacing existing technology, don’t forget that you need to think further than how your current process works today – you need to think about how it might be able to accommodate your business growth, or work across multiple locations, or manage changes in teams. Do you know who your users are?  Developments often fail because no one has thought about the end user. But if you want your software to promote collaboration, open communication and efficiency, you need to have a really clear idea of who will be using it, including their technical capabilities and how it fits with their current work environment and processes. Have you already mapped out the functionalities you want your project to deliver? If your planning is not far beyond “we need a new solution”, then part of the development phase should involve thorough planning. Otherwise, if you go straight into choosing platforms and development without truly knowing your requirements, you could end up needing to do more work (with additional costs) later on.  Does low code meet your needs?  Very complex or bespoke software might be better approached through hand coding. This takes longer – and is therefore more expensive – but it can deliver a completely specialised result. Low code platforms can meet the needs of most process automation, app development, integration and digital transformation projects, but a professional development partner will want to make sure that it will meet your needs. How to choose the right Low Code Development Partner Which low code platform will your developer use?  This is a key question, because not all low code offerings are equal. Platforms that offer good integration, flexibility and scalability are likely to be best for your business if you are looking for reliable technology that will support your business as it grows. There are plenty of online articles about low code platforms – do some research and list the platforms that seem to offer the features you need. Who will own the technology?  Depending on the type of software you are developing, you need to make sure that you will own the technology once it is complete. There are various licensing options available, so it’s worth understanding what these are and working out what is best for your business. How will they support you?  We’ve already said that you will want your technology to scale with your business. So how will that work with your development partner? Will your technology be easy to scale and how will your developer manage new features that become available after your project is finished? These are just some of the things to consider when choosing a low code development partner. Be clear about what you want the software to achieve, and what you want from a partnership and then arrange to chat to a few development teams that have the experience and expertise you need. As an OutSystems partner, we have years of experience in using low code technology to deliver digital transformation solutions to businesses around the world.  Our team has even used OutSystems to build our own commercial waste management software, Waste & Recycling One. So we’re always happy to talk about your project to see if OutSystems and our development approach is right for you – why not give us a call to find out more? Contact us today to find out more. Recommended Posts​ What is low code technology? And why should you consider it? November 22, 2023 What is low code technology? And why should you consider it? Pritesh Pattni The demand

How to adopt a low code digital transformation approach Pritesh Pattni Adopting a low code digital transformation approach Digital transformation is critical to future commercial and organisational success. It updates and streamlines your processes and systems to make your organisation fully customer-driven, using technology to power better experiences for everyone who comes into contact with you.  There’s no argument against the fact that every company should be looking at this – but should you also be looking at a low code digital transformation approach? What is digital transformation? IBM defines digital transformation as an approach that, “… uses AI, automation, hybrid cloud and other digital technologies to leverage data and drive intelligent workflows, faster and smarter decision-making, and real-time response to market disruptions. And ultimately, it changes customer expectations and creates new business opportunities.” Many companies have already embraced digital transformation, or have even built their businesses in a digital-first environment. However, a large number of businesses are still considering the best approach, or have made a start, but are not sure where to go next. Let’s face it, for anything except the simplest business, digital transformation can be complex and time-consuming.  For digital transformation to fully succeed it requires:: detailed analysis and mapping of existing processes and approaches  ensuring you are meeting the relevant regulatory or legislative requirements associated with your business,  adding protections against data theft and other cybersecurity issues researching, testing, assessing and choosing the digital solutions that will form your digital transformation onboarding the new technology, training staff, and managing a cultural process of change. And that’s a lot to consider when your business is also trying to focus on generating new sales, and keeping existing customers happy. So how can you make all of this easier? One area that is gaining popularity is the Low Code approach, so much so that it is already being described as a Revolution. Read our guide on the Low Code Revolution here. What is a Low Code Digital Transformation approach? Whilst Digital Transformation usually involves software and apps that have solutions “out of the box”, most companies will want or need to customise them in some way. A low code development approach is a framework for customised software and app development that has been specifically designed to work without the need for specialist coding knowledge. Think of low code as providing the building blocks of various functions that can then be pieced together to perform a specific task. That way, staff across your business can create, edit and optimise solutions to make their day-to-day work more efficient, without the need for an IT / coding specialist to do it for them. How Low code development enables digital transformation when working with limited resources In many cases, digital transformation is being managed by internal teams – and most often, the IT department. Resources – from personnel to budget – are likely to be limited, and companies want to get the most for every pound, euro or dollar they spend. Add to that the demands of business units, partners, shareholders and customers, and it’s easy to see why companies going through a digital transformation are looking for ways to reduce time and budget while increasing useful output. That’s where low-code digital transformation has a place.  It requires fewer skilled developers and uses dedicated platforms to product technology solutions like web apps and wider software solutions. By using pre-built elements, easy-to-use interfaces and straightforward functionality, it makes building technology faster and easier.  Using low code means you can build strong applications without the long and expensive development cycles often associated with traditional hand coding development. And you are working from pre-existing code libraries that have already been rigorously tested for stability and security.  All of this helps you to manage your digital transformation even with limited resources. Learn more about the differences between low code vs traditional development. Why turn to low-code development? Let’s start with your digital transformation roadmap. This should focus on where you want to be at the end of the process, and the steps you need to take to get there. And it should take into account that there’s no real ‘end’ to this process – it’s all about continuing to give your customers the best possible experience, and making your organisation as efficient as it can be. The reason that increasing numbers of organisations are turning to low code for digital transformation is because it offers the agile, effective solution that they need. Faster development cycles – app development is faster with low code than with traditional hand coding. The nature of low code platforms removes the need for programming, allowing developers to concentrate on getting the user experience right. So not only is your development faster, it’s also more focused. Involve the whole business – historically, development teams have been left alone by other parts of the business because it has been impossible to see what they do. This has hampered collaboration across organisations and meant that expensive technology hasn’t always hit the mark. The easy-to-understand visual nature of low code development means that the IT department can share progress and work with subject specialists, technical experts and business strategists to develop best-in-class applications that deliver to everyone. Your budget goes further – Digital transformation is expensive. So it’s essential that you spend your budget wisely – and have measurable results to show for your spend. Using low code is significantly less expensive than outsourcing to expensive development consultants. You’ll be able to get more functionality, additional advice and better results for your money. Future-proof your business – this kind of transformation is for life, not just for the next year. So any applications you build must be updatable, scalable and able to integrate with the other systems you have now – and anything you might use in the future. The best low code platforms allow integration across a range of other software and technologies, giving you the flexibility you need to ensure your transformation keeps

Why choose low code vs traditional development? Pritesh Pattni There was a time when there was only one option available to companies who wanted to build an app – use traditional hand coding.  As a team of experienced developers ourselves, we know that there are significant benefits of using hand coding to build certain types of software. But there can also be drawbacks, and that’s why we have embraced the emergence of low code platforms too. That way, we are able to offer clients the approach that suits them best – advising on whether to choose low code vs traditional development, no matter where they are in their digital transformation journey.  The pros and cons of traditional development Traditional hand coding might sound old fashioned or archaic – it’s anything but. Talented and experienced developers use programming languages such as Python and Java to create software programmes from scratch. Good traditional development results in highly usable and useful software and it has transformed many processes and commercial offerings. So, hand coding is far from unfashionable – it is just better suited to certain types of development projects. These include particularly complex or customised solutions, where developers need to have complete control over every element. Development can be completely bespoke, but with that comes additional time, resources and costs required in order to fully deliver the solution required. These are some of the reasons traditional development might not be right for your project. So it’s always worth considering both sides before you decide on the right approach for you. For example, hand coding takes a long time. When you are asking developers to write code from scratch, you are asking the team to invest a considerable amount of time and effort into your project. This can extend development cycles – particularly if the team is busy, or you have a change of personnel during your project. It can also be expensive – you are paying for highly skilled developers, often with many years of experience behind them. This costs money, and so you should check whether your budget can absorb these types of costs. And finally, as with all human processes, there’s the potential for errors in the coding. If you are hiring a reliable development team, these can often be avoided, but it’s easy to make a mistake in the code – one that you might not find during testing, but can cause trouble for your end users. Considering the low code option Low code development has been increasing in availability and popularity for several years. Don’t confuse this with no code development, though. No code is where all building is done by using pre-created elements. You don’t need any technical expertise to do it, and you might get reduced functionality because of that. It’s always best to have some development experience on your project, to make sure you are getting the best technology for your needs. Why choose low code? There are several reasons, and for us, the benefits at the top of the list are speed, cost and flexibility. Low code platforms have elements that help to minimise the amount of hand building needed for an app or software development project. They allow integration with other platforms, and developers are able to customise the basic elements to meet the project specifications. Significantly reducing the need for traditional coding by introducing drag and drop modules and a range of other features helps to reduce both time and cost. This supports rapid app development, meaning you can meet new business needs faster, and get to market quickly. Both of these support business growth and good customer service.  Along with this time reduction come positive cost implications. Reduced development cycle time also reduces your spend. And because you don’t need a large team of developers, you’re not paying for all that extra expertise and experience. So your bills should be much more manageable on a low code project.  Flexibility is also important – not just during the development period, but once your solution is up and running. Low code allows for collaboration, so you can discuss and update the application quickly and easily. General maintenance is also faster, and you can build in scalability, so the solution grows with your business.  Learn more about how low code can support your digital transformation journey. Low code vs traditional – which is best?  Although low code sounds like an easy option – and it is – if you’re thinking about low code vs traditional development, bear in mind that a good low code option will also include some developer expertise.  Talk to companies who have a strong development team, because they will take the time to understand what you’re looking for, and help you to design a solution that works technically as well as aesthetically.  If possible, choose a company that partners with one of the recognised platforms – for example, we are an OutSystems partner. You can learn more about the benefits of Outsystems here This means that we have excellent knowledge of how to use the platform to its best advantage, whilst also having the development experience to give you the advice you need. Contact us today to find out more. Recommended Posts​ How to choose a low code platform partner How to choose a low code platform partner Pritesh Pattni If you have a technology project or digital transformation programme, you are probably considering a low code solution. Low code offers a range… Read More What is low code technology? And why should you consider it? What is low code technology? And why should you consider it? Pritesh Pattni The demand for new and upgraded technology isn’t going anywhere. The human race continues to adopt new technologies to… Read More What does it mean to work with an OutSystems Partner? What does it mean to work with an OutSystems Partner? Pritesh Pattni What does it mean to work with an OutSystems partner? When you’re planning a software project, you

Challenging the ‘Spreadsheet mindset’ Pritesh Pattni All businesses use spreadsheets – they are a staple of organisations everywhere. And, while they deliver a wide range of benefits, using spreadsheets for some business processes can be slow and prone to error. That’s why many businesses are considering moving some of the processes currently managed by spreadsheets, onto apps where the goal is typically to improve data accuracy, streamline processes, enhance collaboration. In principle, this sounds like a great idea, and while it will require some up-front investment, it will save money in the longer term. However, there are a few things to be mindful of to ensure the change from a spreadsheet to an app delivers benefits to the business. What is the spreadsheet mindset? This is a term we use to describe the way that some businesses approach replacing spreadsheets with an app. Simply put, it’s when people decide they just need the app to do what the spreadsheet currently does. By replicating the content, formulas and outcomes of the spreadsheet, the business feels it will have accomplished a digital transformation that improves productivity and efficiency. To our minds, there are some fundamental flaws in this approach – flaws that lead to businesses spending a lot of money on app development and just getting a very expensive new spreadsheet for their money. Let’s look at the key dangers of the spreadsheet mindset. You’re recreating something that might not be working – simply turning your spreadsheet into an app won’t transform the way you do things. If you’re struggling with the way your spreadsheet currently works, you need to spend some time considering what you want and how to get there before you spend any money on app development. You haven’t consulted your users – knowing the target audience is one of the most fundamental aspects of app development. Without understanding who’s using the app, you can’t possibly design something that works for them. If a developer agrees to transfer your spreadsheet process to an app without asking about your users, beware. You haven’t thought about the future – designing an app to manage today’s process is good; developing something that is scalable and adaptable for the future is even better. Why spend thousands of pounds for something that might be out of date in 12 months’ time? Many business app failures occur because there’s been no planning for what might come next. You’re jumping on a bandwagon – this is easy for businesses to do, particularly if the competition is adding apps and new technology to their business. But app development is expensive and you need to be able to show a return on your investment. So rather than changing a spreadsheet process to an app just for the sake of it, always make sure you’ve got a clear business case. Why move away from spreadsheets? There are certainly many arguments in favour of ditching spreadsheets. They can be cumbersome and sometimes unreliable. They are difficult to keep secure, and a single error can create chaos. For example, during the 2012 London Olympics, someone on the ticketing team keyed in 20,000 remaining tickets rather than 10,000. So the tickets oversold, and it cost the organisers more than £500,000 to manage the issue. Business leaders know that using spreadsheets can make them vulnerable. They are looking for process solutions that are more secure, more reliable, operate faster and contribute positively to productivity. They want technology that can be used simultaneously by staff members wherever they are, and whatever devices they are using. And apps are the ideal answer. Properly designed and developed, they are an excellent investment, protecting the business for the future, simplifying processes and bringing teams together. How to get it right The first step to successfully transitioning from a spreadsheet to an app is to sit down and plan exactly what you need the app to do. This includes setting out the reasons why the spreadsheet approach isn’t working for you, and considering what your ideal app would look like – both now and in the future. Once you have an outline idea of what you want, you need to find the right development team to work with you. The best option for this type of app is low code – this is where the app is built on a dedicated platform, using a combination of drag-and-drop elements and some traditional coding. Low code delivers a faster build, a reliable solution and the ability to integrate with other systems – without the much larger costs incurred by traditional hand coding. There are lots of low code app developers about, and it can be difficult to know who to work with – particularly if this is your first venture into the world of business apps. So, to avoid getting stuck in an expensive spreadsheet mindset, here are some tips on finding your low code development partner: Which platform do they use? There are a number of low code platforms, and you want to work with a developer who is experienced with a mainstream platform – preferably as a partner organisation. This shows that your development team will have in-depth understanding of the platform, so that they can build the best technology for you. Common platforms include OutSystems, Quickbase, Salesforce, Appian and Microsoft Power Apps. What questions do they ask? In order to build you an app that does everything you need, your development will need to know about your business, the app users, the key processes, future uses and any other processes the app will need to integrate with. The fewer questions your developers ask, the more wary you should be. What experience do they have? There are plenty of low code developers who only focus on taking excel processes and convert them to apps. This might seem like a bonus, but it means they don’t have the wider experience that often comes in useful for building a reliable, useful app. Talk to your developers about the types