Big data analytics adoption is not simply a technology purchase. For industrial organisations and other complex enterprises, it involves matching a business goal to the capabilities of data, systems and people—and then organising the work needed to make those capabilities usable. Affordance theory offers a practical way to examine that process, from identifying possible uses to implementing analytics and assessing early results.
An affordance is a possible action that emerges from the relationship between an actor and a technology or other object. In an organisation, the same analytics platform may offer different possibilities to teams with different goals, experience and capabilities. A structured readiness assessment can therefore help decision-makers see not only what a tool can do, but what the organisation is prepared to do with it.
Big data analytics adoption begins with a business goal
Big data analytics combines tools and techniques to manage, process and analyse data in order to develop actionable insight. The data may be characterised by volume, variety, velocity and veracity; the intended outcome is value. Potential applications include supporting decisions, forecasting sales, customer segmentation, fraud detection and risk assessment.
Those possibilities do not guarantee business results. Before choosing a platform or launching a project, an organisation needs a defined objective and a credible business case. For a manufacturer, for example, a goal such as improving production planning can guide decisions about which data is relevant, what analysis is needed and which teams must participate. The example describes an objective, not a guaranteed outcome.
Affordance theory for big data analytics adoption
The framework distinguishes between the capabilities a technology may offer and the actions an organisation actually takes. It focuses on three connected phases: affordance emergence, perception and actualisation. The resulting effects can then be considered against the organisation’s goals.
1. Emergence: identify what may be possible
Affordances emerge through interaction between organisational actors and technology. Before a technology is adopted, that interaction can take place through vendor discussions, product demonstrations or information gathered from other external sources. The organisation considers possible actions in light of its goals and experience.
Readiness at this stage depends on several practical conditions:
- Data and its properties: The organisation needs to understand its data and how it is managed. Data access, security and privacy policies influence whether information can be used effectively.
- Analytics tools: Tool selection should reflect organisational needs, budget and available skills. Experience with analytics tools can inform the selection process.
- IT infrastructure: The organisation must consider the systems and processes used to collect and store data, as well as whether computing and storage capacity can support the intended work.
- Organisational characteristics: Management commitment, a clear goal and employees’ analytics experience affect which opportunities the organisation can realistically pursue.
2. Perception: recognise relevant opportunities
The possibilities identified during emergence may exceed what an organisation needs or can pursue. Perception is the process of recognising which affordances are relevant to a particular goal. An organisation may overlook an opportunity, misunderstand what a technology can do, or identify a capability that is not accessible under its current policies and processes.
For example, a data policy can clarify access and responsibilities, making potential uses of data easier to evaluate. If the organisation lacks a process for assessing tools or vendors, that gap becomes part of the readiness picture. Decision-makers may need to establish selection criteria or try a demonstration version before committing to implementation. The key is to distinguish an available capability from one that fits the organisation’s needs and constraints.
3. Actualisation: turn a selected affordance into practice
Actualisation is the collective work of making a selected capability ready to use. In an analytics project, that may involve configuring technology, preparing data, assigning responsibilities and developing employee skills. It is an iterative, goal-oriented effort rather than an automatic consequence of choosing a tool.
Planning matters. Teams need to consider project scope, resources, timing and the capabilities required to execute the work. An organisation may use an in-house team, an implementation partner or a combination of both, depending on available expertise. Management commitment, budgeting, employee training and change management can all influence whether the implementation proceeds as intended.
Previous experience also matters. Familiarity with related technology or earlier analytics projects may help an organisation understand requirements and organise the work. Conversely, limited skills or unsuitable infrastructure can constrain what can be actualised. A perceived affordance may also prove incorrect or more difficult to implement than expected, making review during the project important.
Assess early outcomes without confusing them with long-term value
After implementation, immediate outcomes can help teams assess whether the technology is functioning as expected—for instance, whether an adopted analytics tool performs as intended on test data. These concrete results can inform further implementation decisions, but they are not the same as longer-term business effects. Improvements to business performance depend on additional factors and should be assessed in relation to the original goal.
This distinction helps avoid treating deployment itself as proof of success. It also gives project teams a way to connect implementation checks with the larger business case, while recognising that long-term outcomes may take time to evaluate.
What organisational examples reveal about readiness
The cases described in the study illustrate how readiness can vary widely. At ALIMCO, the reported data volume was limited, centres were not integrated, and the IT function had constrained resources and infrastructure. The organisation was still developing its information systems capabilities. The analysis suggested that existing data might support some uses, such as forecasting and production planning, but that broader analytics adoption would require attention to foundational conditions.
By contrast, the multinational bank described had established analytics experience, data policies, integrated infrastructure and employees with relevant skills. Analytics was already used in areas including fraud analysis, risk calculation and data security. The case illustrates how organisational experience and supporting capabilities can make it easier to recognise and pursue further analytics opportunities. These contrasting situations show why a single tool-selection checklist cannot capture every organisation’s readiness.
Use the framework to guide practical decisions
For plant managers, operations leaders, system integrators and technical teams, an affordance-based assessment can structure early planning. Start with the operational goal, then examine data quality and access, infrastructure, tool fit, employee capabilities and management support. Next, decide which potential uses are relevant, what gaps must be addressed and how implementation responsibilities will be organised.
The framework concentrates on technological and organisational factors; it does not include external conditions such as government policy or market factors. Organisations may need to consider those separately when planning an adoption initiative.
In practice, big data analytics adoption is a staged organisational effort, not a decision made at procurement. Affordance theory helps teams connect business goals with what their data, technology and people can enable, while making constraints visible before they become implementation problems. By assessing opportunities, selecting relevant capabilities and planning their actualisation, organisations can approach analytics adoption with clearer expectations and a stronger basis for evaluating outcomes.
Access Official Technical PDF