AIDAOR

The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.
Read more
Article

The AIDAOR model is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision. Compared to the AIDA model the AIDAOR is extended with phases after the purchase decision.


Attention / Awarness

The first step is to attract consumers by creating awareness or affiliation for a service, category, product, or brand. For example, ran a PR campaign in advance.


Interest

Increase potential customer interest by learning about the benefits and advantages of the product. For example, direct mail campaign to offer a free consultation.


Desire

Make the consumer develop an ’emotional connection’. The transition from ‘liking’ to ‘wanting’. For example, local launch events which were previously advertised.


Action

The consumer initiates an action (CTA), the next step. Purchase intention, shopping around, engaging in a trial, etc. Call to purchase on social media sites or a website.


Onboarding

The consumer gets an initial reward. Things needed for the consumer to become a regular. Usage of all the product capabilities like finding related users, integrations, etc.


Retention

Ensuring the consumer stays happy and active. Increasing satisfaction of the consumer over time, long-term monetization, consumer growth, and sharing.


Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
Little's law
Little's law Little’s Law is a theorem for queuing systems. It determines the average number of items in a stationary queuing system