How we give feedback

The Group Code is our short set of ground rules for working together. (You may also hear it called the Builder's Code.) It's not a pledge, and you don't have to call yourself a builder to use it.

The basics:

• Ask first. Before giving advice, try: "Would you like a question, a suggestion, or no feedback right now?" If the answer is no or not now, stop there.
• Stay on the work. Being okay to talk about one piece of work doesn't mean being okay to talk about someone's life.
• Be specific. "The instructions don't say how long it takes" is something you can check. "You never think things through" is a judgment about a person. Talk about actions, not identities or diagnoses.
• Keep it private. Don't repeat someone's story, record them, or take photos without their permission.
• Help, don't rescue. Offer only support you can actually give. Helping isn't policing or monitoring. Accountability partners are separate and optional.

A group vote can never take away someone's right to pass or keep something private. Reviewing the Code doesn't mean giving up any of your rights.

If a boundary gets crossed: The concern contact still needs confirmation from staff.

Journal minimum: Save at least one short note in a Try or Reflect box for this lesson. You do not have to answer every question. Write what you noticed, a question, or what you still do not know. If you have not tried the activity, say so. You can use the example instead of personal details. This leaves something to return to in later lessons. Saving is not sharing.