Varnish, and How Much Is Too Much# SLOP3841 · Week 6 · Nadia Ferrante# Name the bit in the first thirty seconds. Everything already in their Dossier is
varnished — the CV font, the order of the portfolio, the fact that the failed
project is on page two. The question for the next fifty minutes is thickness,
never whether.
I am also varnished. Say so. It buys the rest of the hour.
Nobody assesses your work. They assess your work as presented.# The uncomfortable premise, and the reason this week exists. Presentation is not
an optional layer sitting on top of the work — it is the only channel the work
has. Nobody is going to sit beside you while you explain the commit history.
Do not soften this. The rest of the lecture is only useful if they accept it.
The same project, twice# Bare# rostering-tool
No description. Fourteen commits. The most recent one says fix.
Framed# Shift-clash checker for a 40-person volunteer roster.
Live on a free tier. I wrote the clash logic; the interface is a template.
Nothing about the underlying work differs between these two panels. Same repo,
same fourteen commits, same template interface.
Ask the room which one they would open at four o’clock on a Friday. Then ask
which one they would trust more, and sit with the gap between those answers.
The ninety-second read# An assessor runs four questions, in this order:
What is it
Does it work
Did you do it
Do I care
Present this as observed behaviour rather than folklore — it is what shortlisting
looks like when you have forty tabs open and an hour.
The point for them: these four questions are the specification their artefact is
written against. Anything on the page not answering one of them is decoration.
Thin varnish: four moves#
Name the problem
Show the thing running
State your part
State the constraint
Each move is one sentence, not a redesign. Demonstrate all four live on the
rostering tool from earlier so they see it take ninety seconds, not a weekend.
The constraint is the move everyone skips and the one that does the most work:
“one week, no budget, borrowed data” makes a modest thing legible as a choice.
Thick varnish: four tells#
Adjectives where an outcome should be
No constraint named anywhere
Passive voice arriving at the exact moment of ownership
Finish inversely proportional to depth
Mirrors the previous slide on purpose — same shape, opposite direction. Let the
auto-animate carry that; do not explain the parallel, they will see it.
Flag forward: week 8 red-teams these four tells in their own materials, and times
how long it takes a peer to find the weakest claim. Nobody wants to be timed.
Three surfaces, the same four moves#
Move Repo front page Case study Capability brief The problem First line The brief, verbatim Who has the problem It works A link that runs Before and after A number Your part Commits Your role, named Your decision The constraint Scope note Time and budget What you declined
The gallery walk is organised as these three columns, one per wall. Technical
Practice starts at the repo wall, Creative at the case-study wall, Commercial at
the brief wall, and everyone rotates.
Say plainly that the moves are identical and only the evidence changes. Students
arrive believing their field’s conventions are standards.
Live teardown#
A passionate, detail-oriented creative who leveraged best-in-class tooling to
deliver a seamless end-to-end brand experience for a high-profile client.
Twenty-three words. Four tells. No receipts.
Do this slowly on screen. Ask the room to call the tell before naming it myself —
they find three of the four unaided, and finding it is what makes it stick.
“High-profile client” is the one they miss: it borrows the client’s standing
instead of stating the work, and it cannot be verified by anybody.
Whose work was it# “We” is accurate on a team and useless in an application.
Name your part. Name the parts that were not yours.
Framing what is true is professional practice. Claiming what is not is fraud.
The integrity boundary, said once and then moved past. Overclaiming a team output
is the most common portfolio failure and among the easiest to detect, because the
detail runs out one question in.
No sermon here. State it, take a breath, go to the next slide.
The Varnish Note# Dossier §7. Every presentational decision, what it reveals, and what it conceals.
I moved the group project to the top because it is the only thing with a user
count, which pushes my solo work below the fold.
“Improved layout” is not an entry.
Show the good entry and the useless one side by side and let the contrast do it.
The note is graded on honesty and specificity, never on the materials being
unvarnished.
This is 25% of Assessment 2. Say the number.
Gallery-walk mechanics#
Work on the walls in the first ten minutes
Written critique on the sheet beside it, not spoken across the room
You do not defend your own piece until the final lap
Last twenty minutes: the cross-stream lap
Enforce written critique. Verbal critique leaves no receipt, and the sheets are
the evidence a student cites in their Peer Critique Contribution — Assessment 3,
and the sheet they wrote on today is the artefact.
The no-defending rule is the one that needs restating twice. A defended artefact
stops being read.
Where this lands# Spend the break building, not polishing.
Say the last line twice, once here and once on the way out the door. Thick
varnish is what a fortnight with nothing to build produces.
The break is the only two uninterrupted weeks they get all semester, and it is
directly upstream of the 25% assessment.
Varnish is not a lie. It is a claim about where to look.# Close on the sincere point inside the satirical frame, and stop. No coda, no
recap, no moralising.
If there are questions, take them after the slide is down.