The best way to learn AI is to do it. And the best way to do it is with the support of fellow builders.

Our AI learning cohort starts today with students from around the globe. To help them not just learn, but actually build, we are teaching them the Chipp Feedback Framework.

In short:

Challenge the Work. Support the Builder.

Want to join the cohort? We can catch you up even if you can't make it today. Learn more and sign up here. All registrants have free access to all future cohorts.

Why Feedback Matters

At Chipp, we are builders.

We ship imperfect things.
We test in public.
We iterate fast.
We grow by making.

That only works if feedback is:

  • Honest
  • Generous
  • Specific
  • Forward-moving

Feedback is not evaluation.
Feedback is fuel.

The Core Principle

🎯 Challenge the Work.

🤝 Support the Builder.

Great feedback does both.

Challenge + Support: Why Both Matter

  • Support without challenge
    Feels nice, but doesn’t lead to improvement.
  • Challenge without support
    Feels critical and often shuts people down.
  • Challenge with support
    Builds confidence, clarity, and forward momentum.

The underlying message should always be:

“I see what you’re building. I believe you can make it even stronger.”

The Chipp Feedback Structure

Many years ago I took Seth Godin's Alt-MBA. I was surprised how much emphasis they put on feedback.

After a few weeks, I got it. We are actually horrible at giving feedback. No one teaches us!

And in most businesses and organizations, feedback is reserved for those experienced colleagues.

At Chipp, feedback is for everyone. But, everyone should use this simple format in all cohort reviews:

1️⃣ What I Understood

Show you listened.

  • “Here’s what I think this agent is meant to do…”
  • “The user journey seems to be…”

This builds alignment before critique.

2️⃣ Where I’m Curious

Invite expansion.

  • “I’m curious how this would work if…”
  • “What would happen if a user tried…?”
  • “Is there a reason you chose…?”

Curiosity feels collaborative, not combative.

3️⃣ Where I Got Stuck

Be specific.

  • “I got confused when…”
  • “I wasn’t sure what to do after…”
  • “The CTA felt unclear here…”

Never vague.
Never personal.
Always concrete.

4️⃣ What Might Make This Even Stronger

Forward-looking improvement.

  • “What if you simplified the prompt here?”
  • “Could this use an example?”
  • “Maybe tighten the onboarding flow?”

We are here to improve the work — not label it.

Rules of Great Feedback at Chipp

✅ Be Specific

“Confusing” isn’t helpful.
“Step 2 asks for information I don’t have yet” is helpful.

✅ Speak From Your Experience

Say:

  • “I felt…”
  • “I interpreted…”
  • “I got stuck…”

Not:

  • “Users will hate this.”
  • “This doesn’t work.”

You are offering perspective, not declaring truth.

✅ Separate Identity from Output

Never:

  • “You’re unclear.”
  • “You’re not strategic.”

Instead:

  • “This section could be clearer.”
  • “The positioning might need sharpening.”

We improve artifacts.
We respect people.

✅ Assume Positive Intent

Everyone here is trying to build something meaningful.

Feedback should reflect that assumption.

What Feedback Is NOT

❌ Not scoring
❌ Not ranking
❌ Not proving you’re smarter
❌ Not rewriting someone’s work in your voice
❌ Not fixing everything

You don’t need to solve it.

You need to illuminate it.

How to Receive Feedback Like a Builder

Because this is just as important.

When receiving feedback:

  • Don’t defend immediately.
  • Write it down.
  • Ask clarifying questions.
  • Look for patterns.
  • Decide what to use.

Feedback is input, not instruction.

You are the final decision-maker on your build.

The Culture We’re Creating

Chipp is about:

  • Bold building
  • Fast iteration
  • Real business outcomes
  • AI that works in the real world

That requires psychological safety.

It also requires high standards.

So we practice:

Courageous creativity
+
Respectful rigor

That combination builds great agents — and great builders.

Quick Reference Card (Save This)

When giving feedback, ask yourself:

  1. Did I clearly show I understood the goal?
  2. Did I challenge the work, not the person?
  3. Was I specific?
  4. Did I leave them with a direction forward?
  5. Did my tone communicate belief?

If yes — you’re doing it right.

Learning + Doing

In the Age of AI, anyone can learn anything.

The hard part is taking action.

At Chipp, we favor action. And the best way to help friends, colleagues, and ourselves to take action is with great feedback.

I hope you can join us and use this feedback in our cohorts. Or take it back to your teams to give and receive great feedback.

Just remember:

Challenge the Work. Support the Builder

The link has been copied!