Preparing for AI in Document-centric Processes

Preparing for AI in Document-centric Processes

Mar 9 · 5 min read

Collecting and Structuring Data

You would have to be hiding in a deep, dark place to have missed the rife speculation about the impact of AI. Many AI applications rely on mining existing volumes of data for machine learning and insight. If you believe AI will impact back-office work in a near or distant future, now is a good time to think about where the data will come from. Now is a good time to collect data in a way that makes it easier for a machine to analyze it.

Insofar as organizations stored historical data, many records were stored in an analog format, even if they were originally created with digital tools, and many were documents. Consider letters, contracts, reports and forms created with word processors since the early 1990s.

What happened to them? Invariably, they were printed, signed with ink, and filed – possibly in hardcopy files, but perhaps scanned as PDFs. All remnants of their digital origins were lost, save only for what might be extracted by optical character recognition. Even if records were retained in a digital format, the data was typically unstructured – Word documents, for example, were not designed to store data for machine reading.

AI Impact

The first crop of AI solutions had to mine legacy data, as best it could, with confidence levels that weakened the results. It doesn’t need to be like this.

Without knowing when and what AI will be deployed in future, it’s possible now to collect data that will optimize its future value. If you operate at scale, the value of the data might even become a material contributor to the value of the enterprise. If you create a good store of data, it’s more likely that AI tools can be deployed to reveal insights from your data, rather than data necessarily aggregated from other sources.

The trick is collecting data even when you might not know how it will be used in future. For example, it’s easy to store employee records by the name of the student because a student name is an obvious identifier. Now imagine a future need to analyze employee records to examine all the data, combined with performance data, and identify factors that were predictive of employees more likely to become high performers. Could you do that?

Legito Approach

The Legito approach is to retain all the digital inputs that power back-office automation. In the near term, use the automation to fulfil the functions of your team, including those that include documents.

If you retain the digital inputs throughout your organization processes, you have the best possible data to examine later. Who knows what you will learn, and the value you will add? Data storage is cheap.

Preparing for AI in Document-centric Processes

Mar 9 · 5 min read

Collecting and Structuring Data


You would have to be hiding in a deep, dark place to have missed the rife speculation about the impact of AI. Many AI applications rely on mining existing volumes of data for machine learning and insight. If you believe AI will impact back-office work in a near or distant future, now is a good time to think about where the data will come from. Now is a good time to collect data in a way that makes it easier for a machine to analyze it.

Insofar as organizations stored historical data, many records were stored in an analog format, even if they were originally created with digital tools, and many were documents. Consider letters, contracts, reports and forms created with word processors since the early 1990s. What happened to them? Invariably, they were printed, signed with ink, and filed – possibly in hardcopy files, but perhaps scanned as PDFs. All remnants of their digital origins were lost, save only for what might be extracted by optical character recognition. Even if records were retained in a digital format, the data was typically unstructured – Word documents, for example, were not designed to store data for machine reading.

AI Impact

The first crop of AI solutions had to mine legacy data, as best it could, with confidence levels that weakened the results. It doesn’t need to be like this.
Without knowing when and what AI will be deployed in future, it’s possible now to collect data that will optimize its future value. If you operate at scale, the value of the data might even become a material contributor to the value of the enterprise. If you create a good store of data, it’s more likely that AI tools can be deployed to reveal insights from your data, rather than data necessarily aggregated from other sources.

The trick is collecting data even when you might not know how it will be used in future. For example, it’s easy to store employee records by the name of the student because a student name is an obvious identifier. Now imagine a future need to analyze employee records to examine all the data, combined with performance data, and identify factors that were predictive of employees more likely to become high performers. Could you do that?

Legito Approach

The Legito approach is to retain all the digital inputs that power back-office automation. In the near term, use the automation to fulfil the functions of your team, including those that include documents.

If you retain the digital inputs throughout your organization processes, you have the best possible data to examine later. Who knows what you will learn, and the value you will add? Data storage is cheap.

More Weekly Articles

Automation in Mind? I’d Start with Sales

Automation in Mind? I’d Start with Sales

About Charles Drayson

Charles is a UK lawyer who has used document automation for 20 years. He has worked for large law firms, corporate legal teams, and has automated legal and non-legal documents. He writes for Legito to share his passion for using automation to get work done. “I get a kick out of creating good content and seeing it used repeatedly and reliably by colleagues without fuss and bother”.

Charles Drayson

Feb 22 · 5 min read

Why Sales?

If you have an automation or digital transformation agenda, a Sales project is an excellent place to start. Here’s why.

The first automation project in your organization needs to deliver demonstrable benefits. You want to get off to a good start and have the best chance of success. Organizations might want to do more with automation, but invariably it comes down to just a few individuals who take the initiative and get started. If you are one of those people, there will be talk of ‘low hanging fruit.’ Your first project needs to be at the lower end of complexity: you will be learning as you go, and you want something you can deploy quickly. 

…If there’s any team in your organization that will appreciate a quick deployment of a simple solution that adds fast results, it’s Sales…

The revenue machine has to keep turning – no stoppages, focus on results, and be ready for the next cycle. That’s the source of the impetus you need. Change will still generate challenges, but sales teams tend to be interested in things that will give them an edge. Freeing-up time, minimizing procedural and document overhead will be appealing because it allows sales execs to apply their efforts where they see fit. This is important because the first project needs hearts and minds. Sales teams have no incentive to over-complicate their requirements and will give candid and quick feedback.

Sales teams invariably want everything (and everyone) to move faster. That means Sales teams are ideal candidates for using self-service tools – give them access to what they need on demand. Self-service options are particularly impactful during busy period-end procedures, when sales teams are trying to close deals before the end of the month, quarter or year.

Aim your first solution at tackling the tedious document-related tasks that need to be done right but are perceived as adding unwelcome overhead to the sales process. Generating NDAs, producing bids and proposals, distributing technical materials, and creating contracts – I have yet to meet a salesperson who enjoys those tasks. Often, you can deliver immediate value merely by automating the production of those documents and making them available through self-service. That kind of automation is at the heart of Legito, and it has the extra advantage of setting you up well for the next step.

The Use of Worfklow

Documents are artefacts of a broader business process, internal or external. They are the means of communicating information, permissions, and status from one team to another. In short, documents must flow, not merely exist. They require collaboration, approvals, and feedback loops. Documents are associated with time limits, and overlayed with procedures and compliance requirements. In complex sales, the sales team has to coordinate inputs from several internal teams and meet the demands of several customer teams. After the first step enabling easy production of documents, expand the solution by overlaying workflows, especially approvals. Sales execs often say: “It’s easier to get forgiveness than permission.” It’s time to make it easier to get permissions. That is what automated workflows provide.

The problem with legacy document automation systems (including some of solutions still prominent in the market) is that they do a good job of automating the production of documents but forget that documents don’t exist in a vacuum.

Digital Signatures

If the document authorizations are in place, make it easier for customers to close deals with digital signatures. Digital signature tools are embedded in Legito. It’s becoming increasingly rare to see documents signed with wet ink, and organizations that still use legacy signature processes risk looking outdated. Wet ink signatures take time, are difficult to monitor, and are a nuisance for people who work remotely. It’s helpful to have digital signature capability within Legito because you don’t have to embark on another project to integrate with a separate digital signature tool. The facility is ready for you when you are. This is the philosophy of Legito – we know you won’t use all the tools at the start, but we want them to be ready when you need them without having to leave the solution.

 

An Overview of Deals

Moving on from workflows, you have the data needed to provide an overview of deals-in-progress (for the Sales teams and other stakeholders). The data will be extracted automatically from the documents, so the reports will be reliable. As well as providing information for sales managers, the data used for reporting can also drive alerts and reminders.

After you’ve automated the documents, workflows, reporting, and signing, you can start thinking about the next step from Sales: delivery and contract management. Data can flow to where it’s needed for other teams (operations, finance) using the same solution.

There are precautions to take, as with any automation project. We don’t like to generalize because we know each organization is different, but we have discovered trends associated with successful projects. This article has already proposed a one-step-a-time approach. It’s easier to manage iterative improvements successfully. Don’t build too much at each step. Leave your colleagues wanting more.

Organizations, procedures, teams, and priorities are prone to change. Automation solutions must facilitate change. Refrain from creating unnecessary obstacles to change by automating to such a low level that the system becomes rigid and complex. Moreover, some organizations have procedures that only work because humans know how to mold them – highly prescriptive procedures might be an illusion. Automating a rigid procedure might have unintended consequences. Legito is a human-friendly solution, so leave space for humans to exercise their skill and judgement. Automate only the tasks that are ill-suited to humans. The objective is to augment, not replace, human input. Some industries have compliance or regulatory requirements that demand 100% adherence to a rigid procedure – make those the exception.

The author’s automation experience began with a sales project (working in-house, not as a vendor). The project yielded quick returns, won an industry award, and endured for many years. Behind that project, there was a bargain with the sales team: they had to agree to use the system, but the system had to be useable. It’s a fair bargain to make with colleagues.

Start your digital transformation with Sales, get positive results, and have the ideal base expand and help other teams deliver.

Automation in Mind? I’d Start with Sales

Charles Drayson

Feb 9 · 5 min read

Why Sales?

If you have an automation or digital transformation agenda, a Sales project is an excellent place to start. Here’s why.

The first automation project in your organization needs to deliver demonstrable benefits. You want to get off to a good start and have the best chance of success. Organizations might want to do more with automation, but invariably it comes down to just a few individuals who take the initiative and get started. If you are one of those people, there will be talk of ‘low hanging fruit.’ Your first project needs to be at the lower end of complexity: you will be learning as you go, and you want something you can deploy quickly. 

…If there’s any team in your organization that will appreciate a quick deployment of a simple solution that adds fast results, it’s Sales…

The revenue machine has to keep turning – no stoppages, focus on results, and be ready for the next cycle. That’s the source of the impetus you need. Change will still generate challenges, but sales teams tend to be interested in things that will give them an edge. Freeing-up time, minimizing procedural and document overhead will be appealing because it allows sales execs to apply their efforts where they see fit. This is important because the first project needs hearts and minds. Sales teams have no incentive to over-complicate their requirements and will give candid and quick feedback.Sales teams invariably want everything (and everyone) to move faster. That means Sales teams are ideal candidates for using self-service tools – give them access to what they need on demand. Self-service options are particularly impactful during busy period-end procedures, when sales teams are trying to close deals before the end of the month, quarter or year. 

Aim your first solution at tackling the tedious document-related tasks that need to be done right but are perceived as adding unwelcome overhead to the sales process. Generating NDAs, producing bids and proposals, distributing technical materials, and creating contracts – I have yet to meet a salesperson who enjoys those tasks. Often, you can deliver immediate value merely by automating the production of those documents and making them available through self-service. That kind of automation is at the heart of Legito, and it has the extra advantage of setting you up well for the next step.

 

 

The Use of Worfklow

Documents are artefacts of a broader business process, internal or external. They are the means of communicating information, permissions, and status from one team to another. In short, documents must flow, not merely exist. They require collaboration, approvals, and feedback loops. Documents are associated with time limits, and overlayed with procedures and compliance requirements. In complex sales, the sales team has to coordinate inputs from several internal teams and meet the demands of several customer teams. After the first step enabling easy production of documents, expand the solution by overlaying workflows, especially approvals. Sales execs often say: “It’s easier to get forgiveness than permission.” It’s time to make it easier to get permissions. That is what automated workflows provide.

The problem with legacy document automation systems (including some of solutions still prominent in the market) is that they do a good job of automating the production of documents but forget that documents don’t exist in a vacuum.

Digital Signatures

If the document authorizations are in place, make it easier for customers to close deals with digital signatures. Digital signature tools are embedded in Legito. It’s becoming increasingly rare to see documents signed with wet ink, and organizations that still use legacy signature processes risk looking outdated. Wet ink signatures take time, are difficult to monitor, and are a nuisance for people who work remotely. It’s helpful to have digital signature capability within Legito because you don’t have to embark on another project to integrate with a separate digital signature tool. The facility is ready for you when you are. This is the philosophy of Legito – we know you won’t use all the tools at the start, but we want them to be ready when you need them without having to leave the solution.

An Overview of Deals

Moving on from workflows, you have the data needed to provide an overview of deals-in-progress (for the Sales teams and other stakeholders). The data will be extracted automatically from the documents, so the reports will be reliable. As well as providing information for sales managers, the data used for reporting can also drive alerts and reminders.

After you’ve automated the documents, workflows, reporting, and signing, you can start thinking about the next step from Sales: delivery and contract management. Data can flow to where it’s needed for other teams (operations, finance) using the same solution.

There are precautions to take, as with any automation project. We don’t like to generalize because we know each organization is different, but we have discovered trends associated with successful projects. This article has already proposed a one-step-a-time approach. It’s easier to manage iterative improvements successfully. Don’t build too much at each step. Leave your colleagues wanting more.

Organizations, procedures, teams, and priorities are prone to change. Automation solutions must facilitate change. Refrain from creating unnecessary obstacles to change by automating to such a low level that the system becomes rigid and complex. Moreover, some organizations have procedures that only work because humans know how to mold them – highly prescriptive procedures might be an illusion. Automating a rigid procedure might have unintended consequences. Legito is a human-friendly solution, so leave space for humans to exercise their skill and judgement. Automate only the tasks that are ill-suited to humans. The objective is to augment, not replace, human input. Some industries have compliance or regulatory requirements that demand 100% adherence to a rigid procedure – make those the exception.

The author’s automation experience began with a sales project (working in-house, not as a vendor). The project yielded quick returns, won an industry award, and endured for many years. Behind that project, there was a bargain with the sales team: they had to agree to use the system, but the system had to be useable. It’s a fair bargain to make with colleagues.

Start your digital transformation with Sales, get positive results, and have the ideal base expand and help other teams deliver.

About Charles Drayson

Charles is a UK lawyer who has used document automation for 20 years. He has worked for large law firms, corporate legal teams, and has automated legal and non-legal documents. He writes for Legito to share his passion for using automation to get work done. “I get a kick out of creating good content and seeing it used repeatedly and reliably by colleagues without fuss and bother”.

More Industry Insights

Streamlining HR Processes with the Adoption of Legito

Streamlining HR Processes with the Adoption of Legito

About Charles Drayson

Charles is a UK lawyer who has used document automation for 20 years. He has worked for large law firms, corporate legal teams, and has automated legal and non-legal documents. He writes for Legito to share his passion for using automation to get work done. “I get a kick out of creating good content and seeing it used repeatedly and reliably by colleagues without fuss and bother”.

Charles Drayson

Feb 9 · 5 min read

Through a series of coincidences, I’ve been a close spectator of the workings of HR teams, small and large. I had a fun time as General Counsel for one of the large global outsourcing service providers serving the HR sector. Subsequently, I never seemed far away from projects that directly or indirectly interacted with HR processes.

Of all the back-office functions, HR functions at the confluence of regulation change, procedure and business need – but remains vitally (and ironically dependant on humant input).

Too  much procedure with too little human involvement will fail business needs. Failure to reflect regulatory requirements, or inability to roll with change, leads to the same dysfunction. It’s difficult enough to blend all the requirements in just the right mix, but then you have to add volume.

Some HR tasks require specific solutions. Nobody operates the payroll without a payroll solution, for example. Many HR teams also use more generic HR applications for wider matters like absence management, maintaining HR records, and staff appraisals. Where does an application like Legito fit?

Benefits of Legito Deployment

Legito is an enterprise application – Legito’s strength is the ability to span the needs of the whole organization without loss of utility. Enterprise adoption requires a rich feature set (simple, not simplistic), intuitive use without big change management projects, and the ability to customize the solution for the needs of each team. The HR team’s organizational view is oriented around employees and their place within the enterprise – very different to, say, a finance team or a procurement team. In stark contrast to more specific solutions, we designed Legito to be flexible, to serve the wider audience. Flexibility gives HR teams access to a solution tailored for HR. More than that, the same flexibility has two more benefits: flexibility to reflect your desired way of working within HR, and flexibility to integrate the HR workflows with procedures and teams external to the HR department.

 

Recruitment

Consider a new joiner process, for example. A good new joiner process begins and ends outside the HR team. At one end of the process, hiring managers need to initiate recruitment. At the other end of the process, you need to pass a new joiner’s records to the IT team to provision user accounts and systems access. The handover between the HR team and other back-office teams ought to be integrated. True integration across department boundaries is harder to achieve with disparate systems. It’s harder when those disparate systems evolve, as they must.

Let’s talk about the human dimension for a moment. It’s a rare HR workflow that can be fully automated without adverse consequence. Legito exists to augment the work of back-office professionals, not replace them. Leave space for humans to do what they do best. Legito empowers people in two contexts. Before your first colleague interacts with a Legito solution, someone needs to build it to meet your needs, leveraging the flexibility we mentioned. Cue the citizen developer (we recommend the Gartner definition if you are unfamiliar with the concept).

Legito is built on the premise that the best people to configure solutions are those who know your organization and your needs – your HR professionals, not developers. They are also best placed to ensure your solution keeps up with the pace of change.

 

Implementation Process

Adoption should be facilitated, not imposed. The demand for human-friendly applications is increasing because we have colleagues who consume technology, and they have high expectations. If a solution is awkward, cumbersome or mimics legacy analogue processes, it will disappoint. Use the opportunity to create something you would want to use. Optimize your chances of success by starting with small projects and seek feedback. Legito customers report that adoption is best achieved when colleagues like what they see and ask for more.

Legito case studies tell us that the success of their implementation derives from deploying a solution that is a pleasure to use.

Use of Workflow

HR matters are document-orientated, which makes them ideally suited to the Legito platform. Use rich automation templates to create documents of any complexity, and render them accessible to colleagues who might not have the inclination or knowledge to create them manually. It’s frequently necessary to make sets of documents from one data set with consistency and efficiency. Many Legito implementations will begin with a project based on document automation, often with a positive ROI for simple use cases. Document automation is a solid foundation on which to build.

When you are ready to expand from the first project, the Legito platform supports the end-to-end process. Use workflow to get approvals. Use digital signatures to execute documents. Use document management to store completed documents. Use automatic data extraction to power reminders. Build custom reports for management oversight. All these features are available within the platform without the need to integrate with other applications.

We promote Legito for enterprise-wide adoption, but organizations have to begin somewhere, and the HR team is invariably a good place to start.

Streamlining HR Processes with the Adoption of Legito

Charles Drayson

Feb 9 · 5 min read

Through a series of coincidences, I’ve been a close spectator of the workings of HR teams, small and large. I had a fun time as General Counsel for one of the large global outsourcing service providers serving the HR sector. Subsequently, I never seemed far away from projects that directly or indirectly interacted with HR processes. 

Too  much procedure with too little human involvement will fail business needs. Failure to reflect regulatory requirements, or inability to roll with change, leads to the same dysfunction. It’s difficult enough to blend all the requirements in just the right mix, but then you have to add volume.

Some HR tasks require specific solutions. Nobody operates the payroll without a payroll solution, for example. Many HR teams also use more generic HR applications for wider matters like absence management, maintaining HR records, and staff appraisals. Where does an application like Legito fit?

Benefits of Legito Deployment

Legito is an enterprise application – Legito’s strength is the ability to span the needs of the whole organization without loss of utility. Enterprise adoption requires a rich feature set (simple, not simplistic), intuitive use without big change management projects, and the ability to customize the solution for the needs of each team. The HR team’s organizational view is oriented around employees and their place within the enterprise – very different to, say, a finance team or a procurement team. In stark contrast to more specific solutions, we designed Legito to be flexible, to serve the wider audience. Flexibility gives HR teams access to a solution tailored for HR. More than that, the same flexibility has two more benefits: flexibility to reflect your desired way of working within HR, and flexibility to integrate the HR workflows with procedures and teams external to the HR department.

Recruitment

Consider a new joiner process, for example. A good new joiner process begins and ends outside the HR team. At one end of the process, hiring managers need to initiate recruitment. At the other end of the process, you need to pass a new joiner’s records to the IT team to provision user accounts and systems access. The handover between the HR team and other back-office teams ought to be integrated. True integration across department boundaries is harder to achieve with disparate systems. It’s harder when those disparate systems evolve, as they must.

Let’s talk about the human dimension for a moment. It’s a rare HR workflow that can be fully automated without adverse consequence. Legito exists to augment the work of back-office professionals, not replace them. Leave space for humans to do what they do best. Legito empowers people in two contexts. Before your first colleague interacts with a Legito solution, someone needs to build it to meet your needs, leveraging the flexibility we mentioned. Cue the citizen developer (we recommend the Gartner definition if you are unfamiliar with the concept).

Legito is built on the premise that the best people to configure solutions are those who know your organization and your needs – your HR professionals, not developers. They are also best placed to ensure your solution keeps up with the pace of change.

 

Implementation Process

Adoption should be facilitated, not imposed. Invariably, Legito case studies tell us that the success of their implementation derives from deploying a solution that is a pleasure to use. The demand for human-friendly applications is increasing because we have colleagues who consume technology, and they have high expectations. If a solution is awkward, cumbersome or mimics legacy analogue processes, it will disappoint. Use the opportunity to create something you would want to use. Optimize your chances of success by starting with small projects and seek feedback. Legito customers report that adoption is best achieved when colleagues like what they see and ask for more.

Use of Workflow

HR matters are document-orientated, which makes them ideally suited to the Legito platform. Use rich automation templates to create documents of any complexity, and render them accessible to colleagues who might not have the inclination or knowledge to create them manually. It’s frequently necessary to make sets of documents from one data set with consistency and efficiency. Many Legito implementations will begin with a project based on document automation, often with a positive ROI for simple use cases. Document automation is a solid foundation on which to build.

When you are ready to expand from the first project, the Legito platform supports the end-to-end process. Use workflow to get approvals. Use digital signatures to execute documents. Use document management to store completed documents. Use automatic data extraction to power reminders. Build custom reports for management oversight. All these features are available within the platform without the need to integrate with other applications.

We promote Legito for enterprise-wide adoption, but organizations have to begin somewhere, and the HR team is invariably a good place to start.

About Charles Drayson

Charles is a UK lawyer who has used document automation for 20 years. He has worked for large law firms, corporate legal teams, and has automated legal and non-legal documents. He writes for Legito to share his passion for using automation to get work done. “I get a kick out of creating good content and seeing it used repeatedly and reliably by colleagues without fuss and bother”.

More Industry Insights

Are you solving a problem or a situation?

Are you solving a problem or a situation?

Jan 10 · 3 min read

Seth Godin, in one of his many insightful contributions, describes the difference between a problem and a situation. A problem has a solution, even if you don’t like what the solution entails or maybe you haven’t discovered the solution yet. A situation exists and has no solution, so you need to learn to live with it. Don’t expend energy on resolving situations pretending to be problems.

 New software might be a response to a problem or a situation. Seth’s analysis could help define the objectives and success criteria while managing the expectations of colleagues who might be hoping for a magic fix.

A new software – the key to all problems

Consider your interactions with customers in a B2B business. Unless you enjoy a monopoly or sell low-value commodity items, customers have choices, negotiating power, foibles, procurement teams, and a raft of requirements that make it hard to push them through your version of a standard sales process. That’s a situation, not a problem. As such, it is not apt to be solved by changing your processes or deploying new software. If you invest in new software on the premise that it will solve (overcome) those pesky problems customers throw at you, you are setting yourself up to fail.

Is this a software vendor saying a software solution is futile? Not at all – just don’t expect software to convert customers into compliant purchasers. The rocky road of sales is a situation you must learn to live with. It’s not tidy, reliable, or even convenient. A sales process is one example of a business process you need to manage rather than force. It involves human interaction. Where does software fit into that process?

If you can’t use a fully robotic process, software is only useful if it augments the work done by humans. Set your objectives and define your returns by that metric – don’t have objectives that assume the ‘situation’ will disappear.

How does a good software work?

There are tasks best done by humans and tasks better done by machines. Humans don’t like tedious, repetitive tasks requiring attention to detail. On the other hand, humans don’t like mechanical responses to interactions that need a human touch. Most back office processes (including those where the customer is a colleague in another part of the organisation) are like this, and each end-to-end process is a mixture of tasks.

Good software should therefore work in three contexts:

  • Automate the steps manifestly suited to machines
  • Bring the other tasks to humans in a way that is timely and pleasing for all involved
  • Keep track of the volume and status of all the transactions so the humans are not overwhelmed by data
We are rapidly getting to the stage where software can also contribute in a fourth context: machines can extract insight from volumes of data to provide humans with feedback previously obscured by the noise of day-to-day transactions.

Are you solving a problem or a solution

Jan 10 · 3 min read
Seth Godin, in one of his many insightful contributions, describes the difference between a problem and a situation. A problem has a solution, even if you don’t like what the solution entails or maybe you haven’t discovered the solution yet. A situation exists and has no solution, so you need to learn to live with it. Don’t expend energy on resolving situations pretending to be problems.

New software might be a response to a problem or a situation. Seth’s analysis could help define the objectives and success criteria while managing the expectations of colleagues who might be hoping for a magic fix.

 

A new software – the key to all problems

Consider your interactions with customers in a B2B business. Unless you enjoy a monopoly or sell low-value commodity items, customers have choices, negotiating power, foibles, procurement teams, and a raft of requirements that make it hard to push them through your version of a standard sales process. That’s a situation, not a problem. As such, it is not apt to be solved by changing your processes or deploying new software. If you invest in new software on the premise that it will solve (overcome) those pesky problems customers throw at you, you are setting yourself up to fail.

 

 

Is this a software vendor saying a software solution is futile? Not at all – just don’t expect software to convert customers into compliant purchasers. The rocky road of sales is a situation you must learn to live with. It’s not tidy, reliable, or even convenient. A sales process is one example of a business process you need to manage rather than force. It involves human interaction. Where does software fit into that process?

If you can’t use a fully robotic process, software is only useful if it augments the work done by humans. Set your objectives and define your returns by that metric – don’t have objectives that assume the ‘situation’ will disappear.

How does a good software work?

There are tasks best done by humans and tasks better done by machines. Humans don’t like tedious, repetitive tasks requiring attention to detail. On the other hand, humans don’t like mechanical responses to interactions that need a human touch. Most back office processes (including those where the customer is a colleague in another part of the organisation) are like this, and each end-to-end process is a mixture of tasks. Good software should therefore work in three contexts:

  • Automate the steps manifestly suited to machines
  • Bring the other tasks to humans in a way that is timely and pleasing for all involved
  • Keep track of the volume and status of all the transactions so the humans are not overwhelmed by data

We are rapidly getting to the stage where software can also contribute in a fourth context: machines can extract insight from volumes of data to provide humans with feedback previously obscured by the noise of day-to-day transactions.

More Weekly Articles

Citizen developer explained

Citizen developer explained

Nov 10 · 3 min read

Gartner says “A citizen developer is an employee who creates application capabilities for consumption by themselves or others, using tools that are not actively forbidden by IT or business units. A citizen developer is a persona, not a title or targeted role. They report to
a business unit or function other than IT
1. More people can be citizen developers if they use no code platforms like Legito.

Citizen developers are also users

Using citizen developers, you can quickly identify and make improvements to a business solution. Citizen developers are also users. They will be among the first to see an opportunity to make useful changes or small tweaks to alleviate glitches. Citizen developers want the solution to be the best it can be. They know the changes that are needed to keep track of business developments. You don’t have to wait to requisition a developer from the IT team or an external supplier, and you don’t need to explain the required changes.

Citizen developers will be part of the business team they serve. Colleagues know who they are. If colleagues see something they would like to add or change, they don’t need to hunt around the organisation for someone to lobby, and they don’t need to explain the needs in emails. Colleagues can walk across the office or have a Teams call to talk to a citizen developer in terms they both understand. Water cooler meetings can become a trigger for improvements. Change happens quickly. Citizen developers don’t need lengthy solution specifications.

Back office

Some back office work is routine and risks going unnoticed until it goes wrong. Back office professionals want and need their work to run like clockwork, and to serve the organisation in the most supportive way possible. There’s a big difference between ‘just good enough’ and ‘exactly what we need’. The latter requires the knowledge of an insider and an appreciation of the nuances and exceptions that accompany all back office work. You just don’t get that level of intuition if you rely on traditional developers

Not everyone is suited to be a citizen developers. That’s OK – you need one or two people who have a creative spirit and a spark to make things better, and the confidence to dig a bit deeper within a software solution. Building solutions with Legito is a way to acquire a new skill that gets noticed by their colleagues and management. It’s an opportunity that is not confined to any management level.

Citizen developer explained

Nov 10 · 3 min read

Gartner says “A citizen developer is an employee who creates application capabilities for consumption by themselves or others, using tools that are not actively forbidden by IT or business units. A citizen developer is a persona, not a title or targeted role. They report to a business unit or function other than IT1. More people can be citizen developers if they use no code platforms like Legito.

Citizen developers are also users

Using citizen developers, you can quickly identify and make improvements to a business solution. Citizen developers are also users. They will be among the first to see an opportunity to make useful changes or small tweaks to alleviate glitches. Citizen developers want the solution to be the best it can be. They know the changes that are needed to keep track of business developments. You don’t have to wait to requisition a developer from the IT team or an external supplier, and you don’t need to explain the required changes

Citizen developers will be part of the business team they serve. Colleagues know who they are. If colleagues see something they would like to add or change, they don’t need to hunt around the organisation for someone to lobby, and they don’t need to explain the needs in emails. Colleagues can walk across the office or have a Teams call to talk to a citizen developer in terms they both understand. Water cooler meetings can become a trigger for improvements. Change happens quickly. Citizen developers don’t need lengthy solution specifications..

Back office

Some back office work is routine and risks going unnoticed until it goes wrong. Back office professionals want and need their work to run like clockwork, and to serve the organisation in the most supportive way possible. There’s a big difference between ‘just good enough’ and ‘exactly what we need’. The latter requires the knowledge of an insider and an appreciation of the nuances and exceptions that accompany all back office work. You just don’t get that level of intuition if you rely on traditional developers.

Not everyone is suited to be a citizen developer. That’s OK – you need one or two people who have a creative spirit and a spark to make things better, and the confidence to dig a bit deeper within a software solution. Building solutions with Legito is a way to acquire a new skill that gets noticed by their colleagues and management. It’s an opportunity that is not confined to any management level.

More Weekly Articles