Some projects cannot be shown publicly. Other times there is consent for certain materials, but not for commercial data, internal processes or the identity of everyone involved. Not having a public case study does not mean we have to settle for adjectives.
We can show how we analyze a situation, which questions we ask and how a decision becomes execution. What matters is describing the nature of the demonstration accurately and not attributing results to it that it cannot prove.
What we want visitors to be able to check
“We have a rigorous process” is hard to evaluate without reference points. A comparison between an incomplete brief and a clarified one can show which information is needed. A sample report can explain what is measured and how the limits of the data are discussed.
These materials support claims about how we work. They do not automatically demonstrate the commercial impact of a project. For that, we need real information, context and a sound interpretation of each contribution.
Before choosing the visual, we state the question: do we want to show the quality of an execution, how we think through a problem or the result of an intervention? Each one calls for a different kind of proof.
Three forms, three different limits
| Material | What it can show | What needs to be explained |
|---|---|---|
| An authorized real project | The work done under the conditions presented | Our role, partners’ contributions and the limits of what can be published |
| A sample prepared for presentation | The structure of a deliverable or an interaction | What is for demonstration and what would vary in a project |
| An independent fictional scenario | The reasoning applied to an invented situation | That it does not represent a client or real results |
A sample can be useful even if it does not include every detail of a deliverable. But we have to say enough so the person does not mistake a simplified example for the whole project or for a standard package.
Anonymizing means more than removing the logo
A screenshot can contain names in notifications, addresses, identifiers, figures, fragments of conversations or information in open tabs. Sometimes the combination of industry, period and results can make a project recognizable even without the company’s name.
That is why consent and review apply to the specific material that will be published, in its form and context. We confirm what can appear, what has to be removed and who checks the final version. We do not assume that access to a project includes the right to turn it into public content.
When we do not have the conditions for a safe presentation, we can build an independent demonstration. It uses invented data and a scenario created for the explanation. We do not try to hide a real client behind cosmetic changes.
A complete demonstration, without invented results
Imagine a fictional workshop that receives inquiries through a form. In the demonstration, a test inquiry lands in a list and is given an owner and a next step. We show what happens when the person responsible is missing.
We can explain the choices: why we need an assignment rule, what information has to be passed on and why confirming receipt does not prove that the inquiry was handled. We can show a complete case, an incomplete one and a duplicate.
What can we claim? That the demonstration illustrates a possible process and its checks. What does not follow from it? That we increased a client’s sales or that every business needs the same system. Those conclusions require other proof.
The “fictional scenario” label has to be visible in the material and in its variations. If we cut the demonstration into a short video, we keep the necessary context. We do not hide the explanation on a page the audience may never visit.
We show the decision, not just the final screen
A final page can be attractive without revealing the problem it solved. A short comment can explain why we reorganized the information, which alternative we considered and why we chose the form shown.
We do not need to publish every internal document. We pick a few decisions that are relevant to the client and connect them to the intended effect. For example, moving delivery terms next to the offer can be explained as an attempt to make the cost easier to evaluate. Without data, we do not present it as a proven increase in conversion.
We can also show the limits of an alternative. This helps visitors understand that the solution was chosen for a specific situation, not because there is only one right way to build any project.
Publishing needs an owner
The team producing the material checks the copy, the images and the exported files. The people who know the project confirm the information and the limits of the consent. Responsibility should not be left in a vague exchange of messages.
We keep a record of the approved form and the agreed uses. If the context changes or the material is withdrawn, we need to know where it appears. This organization also helps maintain the portfolio.
At NOT MORE., we can turn the work and the reasoning behind it into case studies, demonstrations, copy, design and video. We can also create independent scenarios for services that do not yet have a public example. We choose the form based on what it can support, not on the impression of success it might create.