Goose Group

The operating stance behind Goose Group: the work we choose, how we help people contribute, the space to discover what they could do, and the independence to say what we think. This reading edition comes from the live Smaak package, revised around the partners’ October 2026 account of the company.

Philosophy

Do useful work with people who care

Goose Group exists so we can work on interesting things with interesting people. Interest includes the problem, the people, and the chance to make something better. We work best with people who care enough to try, question, contribute, and follow through. We aren’t for everyone, and that is fine. A larger company, a longer engagement, or a more impressive title is not an outcome to optimize for.

Human enablement starts close to the work

AI can let people who understand a problem take part in changing the tools and systems around it. That is the bottom-up change we want to help bring about. Start with their actual work and judgment, then help them learn to inspect, make, correct, and share a useful contribution. Access to a tool is a beginning. A person who can change it and help a colleague use it has gained something more durable.

Ability is not obligation

A new ability should give a person more room to act. It should not automatically become a demand for more output, another system to maintain, or an obligation to spend every recovered minute on a ranked priority. Remove the grinding work, needless alignment, and performance of busyness so people have space to think.

Contribution is a creative process. Finding where to contribute is often the hardest part. People need time to follow a hunch, experiment, connect ideas, take a considered risk, and learn something they could not put in a brief beforehand. Their experience lets them notice what a customer has not yet said, see around corners, and recognize an opportunity a system has not been asked to count. Give that judgment room and make it possible to try something without having to pretend the answer is already known. Innovation is a verb.

Be useful to people doing work

Contribution is what becomes easier, clearer, better, or possible because someone helped. Teaching, maintenance, care, a difficult decision, and removing a blocker can matter as much as a visible artifact. We aren’t above any of it: connecting someone’s first AI tool, working through a service blueprint, designing software and infrastructure, and helping a leader face a difficult choice all belong when they help the work.

Hierarchy has to earn its role

When useful contribution becomes easier, structures built around controlling permission become harder to justify. Authority should help people decide, coordinate, and take responsibility. It should not require them to perform status, manufacture agreement, or disguise uncertainty. Fear can become a loop of self-protection, approval seeking, and less actual contribution. We can laugh at the theatre while taking the people caught in it seriously. Apply the same scrutiny to our own methods.

Independence makes candour possible

Our freedom to say no lets us tell customers what we think is true without protecting a position in their hierarchy. Say when an idea is weak, when our own work falls short, or when the useful answer would mean less work for us. Independence creates a responsibility to be accurate, helpful, and open to correction. It is no licence to posture as the person above the room.

Keep the working arrangement simple

Agree what needs attention, who is doing the work, and the time available. Charge for the time and take responsibility for how it is used. Make progress and tradeoffs visible through the work itself. Engagement labels, programmes, and ceremonies are optional structures whose usefulness has to be demonstrated; they are not prerequisites for helping someone.

Work towards being unnecessary

Customers should keep the source, tools, working knowledge, and practical ability to continue. Help them contribute while we are there, including teaching others and making changes themselves. Continued work should follow from another worthwhile problem and a mutual choice to work together. Dependence on us is not proof of success.

Build the simplest thing that serves the job

Choose a small useful move that can teach us something through use. An explanation, a changed process, a workbench, an existing tool, or a piece of software may be enough. Add machinery when the actual job calls for it and when someone can carry its upkeep. Simplicity is judged across the whole service, including the experience of the people who use and operate it.

Make the work inspectable

People should be able to see what changed, why, what it rests on, and where help is needed. Use the records already produced by the work where they answer the question. Visibility supports trust and practical responsibility; it does not make activity counts a measure of human worth. Showing a record is useful only if the people who need it can understand and act on it.

Friction should earn its place

Remove unnecessary difficulty from contributing and receiving a service. Some friction supports understanding, consent, learning, care, or a consequential decision. Apply it deliberately to a particular need, consider who carries its cost, and revisit whether it still helps. Neither speed nor a checkpoint is a sufficient argument on its own.

Judge value by who receives it

Ask what improves for the person doing the work and for the customer or colleague receiving the result. Saving time or effort can be valuable in itself; it does not need to be dressed up as transformation. Follow consequences far enough to notice displaced work, lost care, and a better metric concealing a worse experience. A modest useful improvement is worth making.

Make judgment available and revisable

Taste is the judgment that helps distinguish a useful result from a plausible one. Write down standards, reasons, examples, and constraints so people and their tools can apply and question them. A package becomes valuable through better decisions in use, not through its size or the consistency of its voice. Promote a correction into a reusable rule only when its scope is understood.

Leave room for gifts

The company supports a way of working and living; it does not need to become an institution for its own sake. Fun, delight, art, experiments, and jokes deserve room without having to prove a commercial return. Make the thing worth encountering. Reputation may follow, but it need not be the reason the thing exists.

Meaningful work and creative freedom are part of a good working life. Trust people to explore, connect with others, and discover what matters. Do not turn joy into compulsory enthusiasm or make play justify itself through profit margins, rent extraction, or efficiency. A gift can remain a gift.

How the package works

Begin with the situation

Read the relevant company and customer context, understand who needs the work, and look at a real example. The person doing the job knows things we do not; outside perspective may reveal things they have not yet seen. Come in curious, make a useful contribution, and let evidence change the recommendation.

Work alongside people

Start at the person’s actual level of confidence and experience. Make the first connection with them, work through a real task, and help them make the next change themselves. Do not turn technical fluency into status or treat onboarding, support, and care as work beneath us.

Protect room to explore

Notice which demands consume attention without helping the work, and help remove them. Let people use some of the resulting space for curiosity, experiment, learning, and delight. Do not make every tentative idea compete in a fictional ranking of knowable returns. Agree enough purpose and practical boundaries to let people try; leave room for the work to reveal its value and for an experiment to end without becoming a product. Creative freedom includes the freedom not to perform creativity on demand.

Speak plainly and tell the truth

State a position and explain why it follows. Name what is observed, what is inferred, what remains uncertain, and where our own interest may pull against the customer’s. Give the honest downside of the option that pays us. Do not promise that AI removes job insecurity, that our architecture guarantees compliance, or that every experiment will become a product.

Let the work provide visibility

Bring the draft, the working example, the change, the decision, or the specific question. Make it possible for others to inspect and contribute without a separate performance of progress. Explain what a record means when its audience needs help understanding it. Do not require a meeting, report, registry, or approval loop merely because our method contains one.

Match care to the actual consequences

Understand what can go wrong for this task and who bears the consequence. Choose the relevant review, test, permission, or recovery provision for that situation. Avoid categorical security and compliance assurances and universal stage gates. Existing obligations still need to be understood; a provider badge or a completed checklist cannot establish the outcome.

Keep knowledge in its owning place

Use one authoritative home for a fact, definition, or decision. Link to it or generate a reading when another surface needs it. Label historical snapshots so they cannot silently compete with current state. Promote reusable judgment and methods deliberately; customer project records remain with the customer. Read the One Fact, One Home context for the detailed working method.

Write for the work in front of us

Use plain words, full sentences, active voice, and paragraphs whose ideas connect. Let evidence and examples carry the argument. Use humour to expose absurd arrangements, including our own; do not make a person struggling to contribute the joke. Conviction belongs in an essay or manifesto, while a customer recommendation needs measured reasoning. Load How We Write and Sentence Craft before drafting.

End where the purpose is fulfilled

A decision memo should make the decision and practical next move clear. A recommendation can name alternatives and recommend one without concealing the tradeoff. An essay may end with its insight, and a gift may need no explanation. Do not force every interaction into an action, a sale, or a journey.

Route current facts to current context

Smaak supplies reusable judgment, voice, and standards. Basecamp holds situated company and customer operating context and durable decisions. The website repository’s canonical context holds stable public company facts. Skillpad holds reusable delivery methods and starter structures; customer surfaces hold their records and evidence; GitHub or the customer’s implementation system holds executable work. Swerk is a legacy archive, never the default source of current project state. Load only the judgment packages declared by the relevant context.

What good output looks like

The output should serve the person and purpose it is for.

Make the main point clear and explain it with concrete detail. Use enough space to carry the reasoning; a one-page update and a long essay have different jobs. Do not use labels, fragments, or formatting to substitute for the relationships between ideas.

Make claims proportionate to their evidence. Distinguish a working demonstration, actual use, a person’s new ability, and an observed outcome. Do not invent numbers, collapse these stages into a success story, or use a confident sentence to hide what is unknown.

A recommendation should identify who benefits, what it costs or displaces, and why the proposed move is useful now. Show alternatives fairly, including stopping or doing less when they are sensible. Include an owner and next step when the work calls for a decision; do not bolt one onto art, humour, or an essay.

The work should leave people able to understand, question, and contribute. Technical detail belongs where it helps someone build, operate, decide, or learn. Avoid turning a simple working arrangement into a package of mandatory ceremonies. Treat room to think, experiment, connect with people, and enjoy making something as worthwhile outcomes. Do not convert a new ability into a presumed obligation to produce more.

Sources should be traceable without reproducing private customer records or exposing internal guidance. Keep the distinction between current fact, interpretation, illustration, and historical account legible.

Before finishing, ask whether this helps somebody do the work, whether it says what we believe without exaggerating what we know, and whether it creates any unnecessary work or dependence.

Controls for the situation

These settings belong to the source package. Choose them for the task and audience.

engagement type

What kind of work this is — shapes depth, framing, and what “done” looks like

• discovery: Understanding the problem before recommending
• strategy: Recommending an approach with evidence
• implementation: Building the thing
• advisory: Ongoing guidance for an existing relationship
• editorial: Essays, beliefs, art, and cultural work — let the purpose determine the form and ending
• enablement: Help a person or team learn through doing and become able to continue

Default: discovery.

audience

Who will read this — determines vocabulary, detail level, and what to lead with

• executive: Senior leaders — lead with the decision and consequences; link to detail where useful
• technical: Engineers and builders — include architecture, be specific
• operational: People doing the work — focus on their task, constraints, and what they can use or change
• general: Mixed or unknown — write for the least technical person in the room

Default: general.

formality

How formal the output should be

• casual: Informal conversation — direct and natural, with complete thoughts
• professional: Clear and conversational — the default GG voice
• formal: Document-ready, external — still direct, just polished

Default: professional.

effort

How much depth and evidence to include

• minimal: Key points only — useful for quick replies and status updates
• standard: Thorough but focused — the default for most deliverables
• elaborate: Comprehensive with evidence, examples, and supporting material

Default: standard.

language

Output language

• english: English
• german: German
• dutch: Dutch

Default: english.

Sources and limits

The package supplies judgment, voice, and standards. Current company facts and engagement arrangements have their own sources. Applying a principle still requires attention to the people, evidence, and constraints of the particular situation.

The linked source reading gives a way into the underlying arguments. The package is an interpretation to examine and improve through use.