The Bette Davis Customer Expectation Formula

bette-davis-customer-expectation

Bette Davis, the actress, had a habit of repeating back to Directors exactly what they asked her to do.

She explained in her biography that she did this to confirm her understanding.

Some directors thought she was pushy, difficult as a result. And she was. But she wanted to be sure, and that there was no assumptions on either part. Then she’d do here lines.

Most of us wouldn’t.

Instead, we’d say our lines and hope we got it right.

So, if Bette Davis wasn’t afraid to get clarification, why should you?

Ever heard a new customer begin to say this?

“That’s not what I was expecting…”

It’s not something you want to hear from customers.

There shouldn’t be any expectations.

Expectations imply assumptions.

What the customer is saying, in a roundabout way, is,

“My idea of what you’d be giving me is different from what’s in front of me. Please try again.”

Maybe they don’t even say please.

Let’s unpack this.

It’s about customer expectations.

Customers imagine how something will be designed if you don’t clarify what you plan to make.

Actually, that’s not true. Maybe you did.

But, here’s the problem.

Did they acknowledge it?

When you left the meeting were you 1000% sure you knew of what you had to build?

Were they 1000% clear on what they were getting?

How did you confirm this?

If you didn’t get cast iron confirmation, don’t leave the meeting until you both agree – exactly – on what will be delivered.

This may make you uncomfortable. You don’t want to seem pushy, especially if it’s a new client.

But what will happen if you don’t?

You’ll spend days, weeks, or more designing, coding, writing and it will never hit the mark.

How can we avoid this?

If you’re building a product, follow these steps:

  1. Create a product matrix in Excel.
  2. List what is in scope.
  3. List what is out of scope.
  4. Prioritise each feature as High, Medium, or Low.
  5. Assign each feature to a delivery date.
  6. Describe each feature as exactly as possible.
  7. Assign a status to each feature, such as in development, in review, finished.

Next, get your client to read this either with you or over a Skype call.

Your aim is to make sure there is no ambiguity.

Once you iron out ‘assumptions’ you can work on your product knowing that you won’t get ambushed with expectations.

Thousands of templates to jump start your project

Acceptance Test Plan

Contingency Plan

Software Development Templates

Acquisition Plan

Conversion Plan

Software Requirements Specification

Action Plan

Cost Benefit Analysis

Software Testing

API Documentation

Database Design

Standard Operating Procedures (SOP)

Audience Analysis

Datasheet

Statement of Work

Availability Plan

Deployment Plan

System Administration Guide

Bill of Materials

Design Document

System Boundary

Business Case

Disaster Recovery Plan

System Design Document

Business Continuity

Disposition Plan

System Specifications

Business Plan

Documentation Plan

Technical Writing Templates

Business Process

Employee Handbook

Test Plan

Business Requirements

Error Message Guide

Training Plan

Business Rules

Expression of Interest

Transition Plan

Capacity Plan

Fact Sheet

Troubleshooting Guide

Case Study

Feasibility Study

Use Case

Change Management Plan

Functional Requirements

User Guide

Communication Plan

Grant Proposal

Verification and Validation Plan

Concept of Operations

Implementation Plan

White Papers

Concept Proposal

Installation Plan

Work Instructions

Configuration Management Plan

Interface Control Document

Software Development Templates

Acceptance Test Plan

Maintenance Plan

Software Requirements Specification

Acquisition Plan

Market Research

Software Testing

Action Plan

Marketing Plan

Standard Operating Procedures (SOP)

API Documentation

Needs Statement

Statement of Work

Audience Analysis

Operations Guide

System Administration Guide

Availability Plan

Policy Manual

System Boundary

Bill of Materials

Project Plan

System Design Document

Business Case

Proposal Manager Templates

System Specifications

Business Continuity

Proposal Template

Technical Writing Templates

Business Plan

Quality Assurance Plan

Test Plan

Business Process

Release Notes

Training Plan

Business Requirements

Request for Proposal

Transition Plan

Business Rules

Risk Management Plan

Troubleshooting Guide

Capacity Plan

Scope of Work

Use Case

Case Study

Security Plan

User Guide

Change Management Plan

Service Level Agreement (SLA)

Verification and Validation Plan

Communication Plan

Setup Guide

White Papers

Concept of Operations

Social Media Policy

Work Instructions

Concept Proposal

Contingency Plan

 

Configuration Management Plan

Conversion Plan