The operating record

Culture is what happens when the work gets difficult.

These are not values for a wall. They are the behaviours we expect to see, practise and improve.

We care about the room

Whether it is an event room, design review or partner call, the quality of who is present and how they participate matters.

We make ideas visible quickly

A rough prototype discussed today is more valuable than a perfect idea hidden for three weeks.

We challenge without humiliating

The work can be criticised directly. The person should still feel respected.

We do not confuse activity with progress

Busy calendars, long calls and dozens of messages are not proof of good work.

We protect the standard

Good enough is acceptable for experiments, not for work presented as final.

We document what we learn

Every project should leave behind better systems for the next one.

We earn trust repeatedly

Trust is the result of doing what was promised, especially when inconvenient.

We keep the exchange clear

Compensation, scope, time and ownership are stated before anyone applies.

What Capvise expects

Selection is a two-way test.

Prestige requires standards. You do not need to know everything; you do need to improve quickly and treat small tasks with the seriousness of visible ones.

01 · Ownership

Observed in the work, not claimed in a form.

02 · Judgement

Observed in the work, not claimed in a form.

03 · Reliability

Observed in the work, not claimed in a form.

04 · Taste

Observed in the work, not claimed in a form.

05 · Candour

Observed in the work, not claimed in a form.

06 · Learning velocity

Observed in the work, not claimed in a form.

07 · Respect for the work

Observed in the work, not claimed in a form.

08 · No spectator mentality

Observed in the work, not claimed in a form.

A working week

Enough structure to do meaningful work.

01

Monday

A short operating review: priorities, blockers and decisions.

02

Tuesday

Independent project work with access to previous material and context.

03

Wednesday

Feedback focused on the work, not performative status reporting.

04

Thursday

Cross-functional exposure to an event, partnership or product discussion.

05

Friday

Iteration, documentation and a short reflection on what changed and why.