Resources

Everything published here, organised by what you are trying to do.

Frameworks, templates, playbooks, blueprints, and assessments. This page exists to route you to the right format rather than to be read end to end.

Free

No signup on anything in this collection

Format-led

Organised by what you need to produce

Runnable

Each format ends in something you can execute

Introduction

Which format solves which problem.

The formats here are not interchangeable. A template captures decisions for one artifact; a playbook orders a sequence; a blueprint covers moving work between two named systems; a framework defines a measurement; an assessment gives a directional estimate in ten minutes.

Picking the wrong format is the most common way this content wastes someone’s time — reading a research framework when the actual need was a two-hour decision session, or filling in a template when the constraint was that nobody agreed which system was authoritative.

Formats
Five
Cost
Free, no signup
Deepest
Research frameworks
Fastest
Interactive assessments

Why this exists

Most resource libraries are organised by topic, which is the wrong axis.

Topic-organised libraries assume you know what you are looking for. In practice people arrive knowing the problem and not the format, and topic navigation makes them read three wrong things before finding the right one.

The useful axis is what you need to produce next: a decision, a sequence, a measurement, an estimate, or a connection design. That is how this page is organised.

You're likely here because

  • You know the problem and not what to read
  • You have read several things and produced nothing
  • A decision is blocked and it is unclear on what

How to choose

Pick by what you need to produce.

If

You need decisions recorded before a build

If

You need to know what order to do things in

If

You need to connect two named systems

If

You need a defensible measurement

If

You need a rough number in ten minutes

How it works

How the formats fit together.

Most real projects use several in this order.

01Estimate02Sequence03Decide04Design the connection05Measure

Step 01

Estimate

An assessment gives a directional read fast, and shows which assumption is doing most of the work.

Step 02

Sequence

A playbook tells you what has to be settled before the next decision is answerable.

Step 03

Decide

A template records the decisions — ownership, authority, boundaries, completion — that the build depends on.

Step 04

Design the connection

A blueprint covers the specific failure modes of the two systems being joined.

Step 05

Measure

A framework turns the result into a reading that is comparable to your own later readings.

Scope

Honest notes on this collection.

  • Nothing here is gated, and nothing requires being a customer.
  • These are written for practitioners rather than for buyers, which makes some of them slower reading.
  • Where a resource assumes a decision has been made, it says so rather than covering everything.
  • Sector-specific regulatory obligations are out of scope throughout.

FAQ

Questions about this collection.

Where should I start?

With what you need to produce next rather than with a topic. The selection guide above is the fastest route; if none of it fits, describing the problem to ARIA is quicker than reading further.

Is any of this gated?

No. No signup, no email, no customer requirement.

What is the difference between a template and a playbook?

A template is the artifact for one decision set. A playbook is the sequence — which template to reach for and when.

Are these UbiVibe-specific?

Mostly not. The decisions, sequences, and measurements apply regardless of what executes the workflow. Where something is product-specific we say so.

How often is this updated?

When the underlying approach changes rather than on a content calendar.

Can I use these commercially?

Yes — use and adapt them internally. They exist to be used rather than admired.

Start with ARIA

Ask ARIA about resources.

You do not have to pick your way through this collection to get started. Describe the outcome you want and ARIA determines which capabilities, systems, and workflows the job needs.

  • ARIA acts only through the systems and permissions you connect.
  • Connections use scoped credentials you can change or revoke.
  • Actions are recorded, and consequential ones can require approval.

Goes to UbiGrowth, with the page you asked from attached. We do not sell or share it. Prefer to talk? Call 972-823-1294.

Start here

Skip the reading if you already know the problem.

Describe what you are trying to get done. ARIA resolves it into an objective and an execution path, which is usually faster than finding the right document.