{"course":{"slug":"independent-creative","title":"Working for Yourself","url":"https://addaly.com/learn/independent-creative","level":"intermediate","track":"create"},"lesson":{"slug":"showing-the-process","title":"How much process to show, and to whom","url":"https://addaly.com/learn/independent-creative/showing-the-process","position":13,"of":84,"minutes":8,"answer":"Keep a process image only when it explains a decision the finished work does not explain by itself, put the finished work first because that is what earns the scroll.","keyIdea":"Keep a process image only when it explains a decision the finished work does not explain by itself, put the finished work first because that is what earns the scroll, and never publish a rejected route you would not want to be hired to repeat."},"body":{"format":"markdown","text":"## Two readers, opposite needs\n\nThere is a permanent argument about whether portfolios should show process. It is unresolvable as stated, because two different buyers are reading the same page with opposite requirements.\n\nA studio hiring you as a contractor wants process. They are trying to work out whether you can think, because they already have people who can execute, and they will be handing you ambiguous briefs. Show them only polished finals and they cannot tell your work from a template purchase.\n\nA shop owner commissioning a sign wants the opposite. Process makes them anxious. Twelve rejected routes tell them the outcome was uncertain, and they are already nervous about spending money with a stranger on the internet. They want to see finished things that look like the finished thing they want.\n\nSo the question is never \"should I show process\". It is \"which of these two people am I trying to reach\", and then: what is the smallest amount of process that makes the case to them.\n\n## The test for keeping a process image\n\nKeep a process image only if it explains a decision that the final work does not explain by itself.\n\nThat is a hard test and most images fail it. A grid of thirty thumbnail sketches does not explain a decision; it demonstrates effort, which nobody is buying. A photograph of your desk explains nothing. A mood board explains nothing to anyone but you, because mood boards are compressed references whose meaning lives in your head.\n\nImages that pass the test:\n\n- **A side-by-side of the constraint and the response.** The original shopfront photographed at dusk, next to the new mark at the same distance and light. This explains why the letterforms got heavier.\n- **A rejected route with one line about why it lost.** \"This version tested badly with older customers, who read the abstract mark as a different shop.\" This is the single most persuasive kind of process image, because it shows judgement rather than production.\n- **A technical diagram the outcome hides.** The colour separation, the die line, the responsive breakpoints, the frame where the animation had to hold for the voiceover.\n\nThree to five images that pass the test beat forty that do not, and they beat them on the same page for the same reader, which is the part people find counter-intuitive.\n\n## The ordering that works\n\nPut the finished work first. Always, for both readers.\n\nThe reason is mechanical: on a portfolio page, most readers decide whether to continue within the first screen, and the finished work is the only thing that earns the scroll. Process-first case studies (opening with research photos and sticky notes) lose the audience before the payoff, and they lose the studio reader too, who has forty portfolios to get through and is scanning for a reason to stop.\n\nSo: hero image of the finished thing, a short line of context, then process, then more finished work, then the write-up. Anyone who reaches your process images has already decided the outcome is good enough to be curious about how it happened. That is the only state in which process is interesting.\n\n## The specific trap: showing work you do not want\n\nEvery rejected route you publish is a route somebody might ask for. This happens more than people expect. You show three directions, note that the client chose the third, and the next enquiry says \"I liked the second one in your bakery project, can you do something like that for us\".\n\nSometimes that is fine. Sometimes the second route was a weak idea you included for contrast, and now you are being hired to repeat your own worst work. If you would not want more work like it, do not put it on the internet. This applies to finished pieces too, and it is the single most common reason an established freelancer's enquiries drift away from the work they want: the portfolio is a menu, and people order from menus.\n\n## Doing it for nothing\n\nProcess documentation costs nothing but attention, and attention is the thing you will not have at the end of a project.\n\nThe practical habit: at the moment you finish each stage, export one image and drop it in a folder named for the job. Not later. At the end of a project the intermediate files are buried in versioned folders with names like `final_v7_ACTUAL.ai`, and reconstructing the story takes an afternoon you will never spend.\n\nFor screen capture on a phone or laptop, whatever is built in is enough. For desktop screen recording, OBS Studio is free on every platform and records a 1080p timelapse of you working without a watermark or a time limit; the paid alternatives at this task buy you convenience, not capability. For mocking up a printed piece, Blender is free and will render a folded carton or a book in context far better than a flat photo.\n\nOne caution on timelapses: a 45-second speed-up of you drawing is satisfying to watch and communicates almost nothing about your judgement. It performs well on social platforms, which reward watching, and poorly with buyers, who are hiring a decision-maker. Make them if you want reach. Do not confuse the reach with enquiries.\n\n## The limitation\n\nProcess pages have a failure mode nobody warns about: they make ordinary work look considered. A designer who documents heavily can present a mediocre outcome wrapped in enough reasoning that it reads as rigorous, and some buyers will be persuaded. This works until the second project, when the work has to be good rather than well-explained.\n\nThe check on yourself is simple. Cover the words. Look only at the images. If the finished work does not hold up in silence, the process pages are not a strength: they are a defence, and you are the person they are defending against."},"check":{"question":"A freelancer keeps receiving enquiries for a flat illustrative style she included only as a contrast option in one case study's rejected routes. She does not want that work. What does this demonstrate about process pages?","options":[{"text":"Published rejected routes function as offerings, so anything you would not want more of should not be on the page at all.","correct":true},{"text":"Rejected routes should be shown without any explanation of why they lost, so readers understand they were not selected and do not request them.","correct":false,"tempting":"Removing the reasoning makes the image less useful and does not stop the request: the picture is what triggers the enquiry, not the caption."},{"text":"Process images should be placed after the written case study rather than before it, so that only committed readers who understand the context ever see the rejected work.","correct":false,"tempting":"Ordering affects how many people see it, not what they do when they see it, and the enquiry came from somebody who did reach the page."},{"text":"The enquiries prove the rejected route was actually the stronger idea, and the real lesson is that the client's choice was wrong and she should reconsider presenting it as rejected.","correct":false,"tempting":"Reads market demand as a verdict on quality. Demand for a style says what buyers recognise, not what solved that particular brief."}]},"prev":{"slug":"no-clients-no-problem","title":"Making work when nobody has hired you","url":"https://addaly.com/learn/independent-creative/no-clients-no-problem"},"next":{"slug":"mockups-and-honesty","title":"Mockups, and where they start lying","url":"https://addaly.com/learn/independent-creative/mockups-and-honesty"},"authorship":"Founder and series editor: Dr Mustafa Mun. Written by AI models to a written standard. Exam keys checked blind by a second model: 3,665 of 3,666 agreed. Academic review invited.","review":{"status":"Draft, open for academic review"},"cite":"Addaly (2026) 'How much process to show, and to whom', in Working for Yourself. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/independent-creative/showing-the-process (Accessed: 13 October 2026).","licence":{"name":"CC BY-NC-SA 4.0","url":"https://creativecommons.org/licenses/by-nc-sa/4.0/"},"reader":{"schema":1,"title":"How much process to show, and to whom","courseTitle":"Working for Yourself","module":{"index":2,"slug":"work-you-can-show","title":"Work you can show"},"answer":null,"keyIdea":"Keep a process image only when it explains a decision the finished work does not explain by itself, put the finished work first because that is what earns the scroll, and never publish a rejected route you would not want to be hired to repeat.","hero":{"kind":"plate","image":null,"alt":null,"caption":null},"blocks":[{"t":"h2","id":"two-readers-opposite-needs","runs":[{"text":"Two readers, opposite needs"}]},{"t":"p","runs":[{"text":"There is a permanent argument about whether portfolios should show process. It is unresolvable as stated, because two different buyers are reading the same page with opposite requirements."}]},{"t":"p","runs":[{"text":"A studio hiring you as a contractor wants process. They are trying to work out whether you can think, because they already have people who can execute, and they will be handing you ambiguous briefs. Show them only polished finals and they cannot tell your work from a template purchase."}]},{"t":"p","runs":[{"text":"A shop owner commissioning a sign wants the opposite. Process makes them anxious. Twelve rejected routes tell them the outcome was uncertain, and they are already nervous about spending money with a stranger on the internet. They want to see finished things that look like the finished thing they want."}]},{"t":"p","runs":[{"text":"So the question is never “should I show process”. It is “which of these two people am I trying to reach”, and then: what is the smallest amount of process that makes the case to them."}]},{"t":"h2","id":"the-test-for-keeping-a-process-image","runs":[{"text":"The test for keeping a process image"}]},{"t":"p","runs":[{"text":"Keep a process image only if it explains a decision that the final work does not explain by itself."}]},{"t":"p","runs":[{"text":"That is a hard test and most images fail it. A grid of thirty thumbnail sketches does not explain a decision; it demonstrates effort, which nobody is buying. A photograph of your desk explains nothing. A mood board explains nothing to anyone but you, because mood boards are compressed references whose meaning lives in your head."}]},{"t":"p","runs":[{"text":"Images that pass the test:"}]},{"t":"ul","items":[[{"text":"A side-by-side of the constraint and the response.","b":true},{"text":" The original shopfront photographed at dusk, next to the new mark at the same distance and light. This explains why the letterforms got heavier."}],[{"text":"A rejected route with one line about why it lost.","b":true},{"text":" “This version tested badly with older customers, who read the abstract mark as a different shop.” This is the single most persuasive kind of process image, because it shows judgement rather than production."}],[{"text":"A technical diagram the outcome hides.","b":true},{"text":" The colour separation, the die line, the responsive breakpoints, the frame where the animation had to hold for the voiceover."}]]},{"t":"p","runs":[{"text":"Three to five images that pass the test beat forty that do not, and they beat them on the same page for the same reader, which is the part people find counter-intuitive."}]},{"t":"h2","id":"the-ordering-that-works","runs":[{"text":"The ordering that works"}]},{"t":"p","runs":[{"text":"Put the finished work first. Always, for both readers."}]},{"t":"p","runs":[{"text":"The reason is mechanical: on a portfolio page, most readers decide whether to continue within the first screen, and the finished work is the only thing that earns the scroll. Process-first case studies (opening with research photos and sticky notes) lose the audience before the payoff, and they lose the studio reader too, who has forty portfolios to get through and is scanning for a reason to stop."}]},{"t":"p","runs":[{"text":"So: hero image of the finished thing, a short line of context, then process, then more finished work, then the write-up. Anyone who reaches your process images has already decided the outcome is good enough to be curious about how it happened. That is the only state in which process is interesting."}]},{"t":"h2","id":"the-specific-trap-showing-work-you-do-not-want","runs":[{"text":"The specific trap: showing work you do not want"}]},{"t":"p","runs":[{"text":"Every rejected route you publish is a route somebody might ask for. This happens more than people expect. You show three directions, note that the client chose the third, and the next enquiry says “I liked the second one in your bakery project, can you do something like that for us”."}]},{"t":"p","runs":[{"text":"Sometimes that is fine. Sometimes the second route was a weak idea you included for contrast, and now you are being hired to repeat your own worst work. If you would not want more work like it, do not put it on the internet. This applies to finished pieces too, and it is the single most common reason an established freelancer’s enquiries drift away from the work they want: the portfolio is a menu, and people order from menus."}]},{"t":"h2","id":"doing-it-for-nothing","runs":[{"text":"Doing it for nothing"}]},{"t":"p","runs":[{"text":"Process documentation costs nothing but attention, and attention is the thing you will not have at the end of a project."}]},{"t":"p","runs":[{"text":"The practical habit: at the moment you finish each stage, export one image and drop it in a folder named for the job. Not later. At the end of a project the intermediate files are buried in versioned folders with names like "},{"text":"final_v7_ACTUAL.ai","code":true},{"text":", and reconstructing the story takes an afternoon you will never spend."}]},{"t":"p","runs":[{"text":"For screen capture on a phone or laptop, whatever is built in is enough. For desktop screen recording, OBS Studio is free on every platform and records a 1080p timelapse of you working without a watermark or a time limit; the paid alternatives at this task buy you convenience, not capability. For mocking up a printed piece, Blender is free and will render a folded carton or a book in context far better than a flat photo."}]},{"t":"p","runs":[{"text":"One caution on timelapses: a 45-second speed-up of you drawing is satisfying to watch and communicates almost nothing about your judgement. It performs well on social platforms, which reward watching, and poorly with buyers, who are hiring a decision-maker. Make them if you want reach. Do not confuse the reach with enquiries."}]},{"t":"h2","id":"the-limitation","runs":[{"text":"The limitation"}],"role":"limit"},{"t":"p","runs":[{"text":"Process pages have a failure mode nobody warns about: they make ordinary work look considered. A designer who documents heavily can present a mediocre outcome wrapped in enough reasoning that it reads as rigorous, and some buyers will be persuaded. This works until the second project, when the work has to be good rather than well-explained."}]},{"t":"p","runs":[{"text":"The check on yourself is simple. Cover the words. Look only at the images. If the finished work does not hold up in silence, the process pages are not a strength: they are a defence, and you are the person they are defending against."}]}],"check":{"question":[{"text":"A freelancer keeps receiving enquiries for a flat illustrative style she included only as a contrast option in one case study’s rejected routes. She does not want that work. What does this demonstrate about process pages?"}],"options":[{"text":[{"text":"Published rejected routes function as offerings, so anything you would not want more of should not be on the page at all."}],"correct":true,"tempting":null},{"text":[{"text":"Rejected routes should be shown without any explanation of why they lost, so readers understand they were not selected and do not request them."}],"correct":false,"tempting":[{"text":"Removing the reasoning makes the image less useful and does not stop the request: the picture is what triggers the enquiry, not the caption."}]},{"text":[{"text":"Process images should be placed after the written case study rather than before it, so that only committed readers who understand the context ever see the rejected work."}],"correct":false,"tempting":[{"text":"Ordering affects how many people see it, not what they do when they see it, and the enquiry came from somebody who did reach the page."}]},{"text":[{"text":"The enquiries prove the rejected route was actually the stronger idea, and the real lesson is that the client’s choice was wrong and she should reconsider presenting it as rejected."}],"correct":false,"tempting":[{"text":"Reads market demand as a verdict on quality. Demand for a style says what buyers recognise, not what solved that particular brief."}]}],"order":[3,2,1,0],"why":null},"prev":{"slug":"no-clients-no-problem","title":"Making work when nobody has hired you","minutes":9},"next":{"slug":"mockups-and-honesty","title":"Mockups, and where they start lying","minutes":9}}}