CCR // ABSTRACTS
An abstract describes the problem, possibility or question.
The Lab is where we make it tangible.
You don't need the solution yet.
Start with something worth finding out.
ABSTRACTS
What kinds of questions can be explored?
LAB
What does an experiment actually look like?
ABSTRACTS WITH EXPERIMENTS
CAN PEOPLE EVALUATE AI BEFORE AI TOUCHES PRODUCTION?
WHY IT MATTERS
An organization may be interested in an AI-driven customer or employee experience without being ready to integrate it into an established website, application or workflow.
WHAT WE MIGHT TEST
Build enough of the experience somewhere independent for the people making the decision to actually use it.
RELATED ENVIRONMENT
CCR-001 // PROJECT NIGHTHAWK
WHAT IF "LAST OBSERVED" IS ENOUGH?
WHY IT MATTERS
Not every location-related problem requires continuous precise tracking. Could participating wearables interacting with known fixed beacons provide useful proximity information in environments such as campgrounds, camps, resorts or large recreational properties?
WHAT WE MIGHT TEST
Whether the information is useful before determining whether the underlying hardware deserves further development.
RELATED ENVIRONMENT
CCR-002 // PROJECT WAYFINDER
WHAT IF PEOPLE COULD USE THE FUTURE STATE BEFORE APPROVING IT?
WHY IT MATTERS
Some changes are easier to evaluate when people can use the future state instead of speculating.
WHAT WE MIGHT TEST
Build the proposed experience independently while leaving the current website, workflow or application untouched.
RELATED ENVIRONMENT
CCR-003 // PROJECT MIRROR
WHERE DOES THE WORK ACTUALLY GET STUCK?
WHY IT MATTERS
A slow or frustrating process does not automatically need new software. First identify where the friction actually occurs.
WHAT WE MIGHT TEST
Alternative intake, routing, communication or operational workflows without replacing the existing system first.
RELATED ENVIRONMENT
CCR-004 // PROJECT SWITCHBOARD
HOW DO YOU CHANGE SOMETHING WITHOUT BREAKING WHAT STILL WORKS?
WHY IT MATTERS
Old and new systems sometimes need to coexist temporarily. The danger is allowing temporary infrastructure to become permanent simply because nobody owns its eventual removal.
WHAT WE MIGHT TEST
A bounded transition environment with a defined exit.
RELATED ENVIRONMENT
CCR-005 // PROJECT BRIDGE
WHAT STOPS WORKING WHEN THE PERSON WHO KNOWS HOW IT WORKS ISN'T HERE?
WHY IT MATTERS
Important business systems often depend on informal knowledge, individual access, forgotten vendors, old devices, undocumented accounts or responsibilities that exist only in someone's head.
WHAT WE MIGHT TEST
Map the dependencies, identify ownership and perform an absence test.
RELATED ENVIRONMENT
CCR-006 // PROJECT RELAY
MORE QUESTIONS WORTH ASKING
These abstracts do not yet have corresponding experiments. That is intentional.
WHAT ARE WE STILL PAYING FOR THAT NOBODY USES?
WHAT DEPENDS ON A DEVICE NOBODY THINKS ABOUT?
WHO ACTUALLY OWNS THIS VENDOR RELATIONSHIP?
WHAT HAPPENS WHEN A CRITICAL ACCOUNT LOCKS US OUT?
COULD CUSTOMERS ANSWER THIS THEMSELVES?
WHAT INFORMATION DOES EVERY NEW EMPLOYEE HAVE TO LEARN FROM SOMEONE ELSE?
WHAT SHOULD HAVE AN OWNER BUT DOESN'T?
WHAT TEMPORARY SOLUTION QUIETLY BECAME PERMANENT?
NOT SURE WHAT THE QUESTION IS YET?
CCR // LAB
The Lab turns selected questions into environments people can see, use and evaluate.