Honesty & Authorship

We arrive at the question that sits underneath this whole module and, in a sense, the whole course: are you telling the truth? A portfolio is a persuasive document, and persuasion tempts everyone toward the flattering edge of the facts - claiming a bit more of a project than was yours, letting a team effort read as solo, showing an AI-assisted image as if you photographed it, staying quiet about the parts that were not you. Every one of those is a small lie, and small lies in a portfolio are a genuinely bad bet - not only because they are wrong, but because they are the single easiest thing in your whole application to get caught for, and the most expensive to get caught for.

Consider how it actually plays out. A portfolio's claims are tested in the interview, and interviewers test them almost without trying. They ask one honest follow-up question - "how did you resolve that junction?", "walk me through how you got to this plan", "what would you change?" - and a claim you cannot back evaporates in real time, in front of the person deciding your future. The gap between what you implied and what you can actually explain is instantly, physically visible: the hesitation, the vague answer, the pivot. You do not just lose the point; you lose the reader's trust in everything else you said, because now they are re-reading your whole portfolio wondering what else was inflated.

The professions run on this. Architecture and interior design are small worlds, connected by shared studios, shared photographers, shared clients and long memories. The person interviewing you may know the studio whose project you are claiming; your future colleague may have actually done the part you implied was yours. Reputation, which Module 9 treats as a compounding asset, is built or broken on exactly this - whether your account of your own work holds up. A reputation for straightness is worth more over a career than any single dazzling project, and it is destroyed by exactly one caught exaggeration.

So the case for honesty is not only that it is right - though it is. It is that it is self-interested over any horizon longer than one interview. The honest portfolio is the one you can defend, calmly and in detail, to anyone, forever. That is a very strong position to argue from. The inflated one is a bluff waiting for a single question. Choose the position you can hold.

Most of the honesty problem is not dramatic fraud; it is the everyday, easy-to-slide-into ambiguity about your role in shared work - and it has an easy, honest fix. Almost everything you will show early in your career was made with other people: studio projects with teammates, office projects with a whole team and a lead, competitions with collaborators. The reader knows this. What they are testing is whether you can be specific and accurate about your own part - because how you credit shared work predicts how you will behave on their team.

The fix is a vocabulary of honest verbs, chosen to match what you actually did. Led or designed means you owned it end to end - use it only when true, because it invites the deepest questioning. Contributed, developed, detailed, drew, modelled name a real, specific part within a team - this is the honest middle, and most office and studio work genuinely lives here. Assisted, supported, or drew under name a helping role on someone else's project - and a small honest role, well described, is worth far more than a large false one. The skill is picking the verb that would survive the studio it came from reading your portfolio.

Sample lines that are both honest and strong:

Office project, led by the practice. My role: developed
the facade detailing and produced the construction drawings
for levels 3-6. Concept and planning by the design team.

Studio project with two collaborators. I led the site
strategy and the section; my teammates led the plan and
the model.

Competition entry (shortlisted). I produced the diagrams
and the render; concept shared across the team of four.

Notice that none of these diminishes you. Being precise about a real contribution reads as more impressive, not less, because it is credible and it shows you understand where your work sat in a larger effort - which is exactly the maturity a team wants. The temptation is to blur ("Project: [Big Building]. [Your Name]") and hope the reader assumes the flattering reading. Resist it. Ambiguity you intend the reader to misread is dishonesty with deniability, and interviewers are extremely good at spotting it. State your part plainly, credit the rest generously (Module 7.2), and you turn the most dangerous section of your portfolio into the most trustworthy.

AI tools are now part of how design work gets made - for ideation, image generation, drawing cleanup, visualisation, and writing help, including the writing in a portfolio. This is not going away, and using these tools is not, in itself, something to hide or apologise for. But it raises a fresh version of the oldest question - what did you actually do? - and the honest answer matters more than ever, because AI makes it trivially easy to produce polished output you do not understand and could not re-make. The line is not "AI or no AI". The line is whether the judgement is yours, whether you can stand behind the result, and whether you are straight about how it was made.

Some uses are entirely fine, and you should simply be matter-of-fact about them. Using AI to generate options you then judge, edit and develop is design work - the judgement is yours. Using it to help draft or tighten your written descriptions is fine if you have read, edited and can own every line. Producing an AI-assisted render is fine if you label it as a render and not as a photograph of a built thing. The graceful home for this disclosure is the caption and the credit block you already built in Lesson 7.2: "concept render, AI-assisted"; "visualisation generated with [tool], edited by me". Naming the tool costs you nothing and signals exactly the honesty readers are now watching for.

Some uses are not fine, and the boundary is not subtle. Passing an AI image off as a photograph of real, built work is a straightforward lie. Presenting an idea, a form or a resolution as yours when a tool produced it and you merely accepted it is claiming authorship you do not have. Showing work you could not re-make and could not explain - because you do not actually understand how it came to be - is the deepest trap, because it will collapse under the first serious question in an interview, exactly like an inflated role claim.

Here is the practical test, and it is a good one to carry: could you re-make this, and explain every decision in it, in the interview? If yes, the judgement is genuinely yours and you can show it with a clear conscience and a clear label. If no, either do the work until you can, or do not present it as your design. The tools are legitimate; the standard is unchanged. Authorship has always meant "I made the decisions and I can defend them", and AI does not lower that bar - it just makes it easier to pretend you have cleared it. Do not pretend. Be the designer who used a powerful tool well and says so plainly - that reads as confidence and current skill, which is exactly what a modern studio wants.

Step back and see honesty for what it is: not a constraint that costs you opportunities, but a strategy that compounds. Integrity in a portfolio is the same discipline as integrity in practice - and readers are hiring for the second by testing the first. A studio is not only asking "is this person talented?"; it is asking "can I trust what they tell me?", because they are about to trust you with clients, drawings, budgets and their own reputation. Every honest credit, every accurate role, every labelled render is quiet evidence that you can be trusted - and that evidence is worth more than any project.

Hold on to the long view. You will build many portfolios across a career, and the honest one has a property the inflated one never can: it is durable. You never have to remember which version of a story you told; you are never one question away from exposure; you can defend every page to anyone, including the people you worked with, forever. That is a calm, strong place to build a career from. The person who inflated their role, borrowed a studio's shine, or passed off a tool's output is always, quietly, waiting to be found out - and in a small profession, they usually are.

None of this means selling yourself short. Honesty is not the same as modesty, and it is certainly not self-erasure. State your real contributions with full confidence; a precisely described genuine achievement is more impressive than a vague grand claim, not less. The goal is accuracy - claiming exactly what is yours, no more and no less, and being generous about the rest. That combination - confident about what you did, honest about what you did not, generous to those you did it with - is not just ethical. It is the most persuasive posture there is, because it is the only one that survives scrutiny.

So end the module here, on the spine that runs through the whole course. A portfolio is a curated argument aimed at one busy reader - and the strongest argument is a true one, made with a clear voice and an open hand.

> Be honest about your role, generous about your team, and straight about your tools - including AI. Claim exactly what is yours and can defend it, and nothing you cannot. Integrity is not the price of a good portfolio; over a career, it is the whole return.