In this article

Looking at an impressive corporate identity presentation differs from assessing an approach for your project. Portfolio imagery gives a first impression; understanding the system means examining relationships between applications. How does the mark behave across surfaces, is information organised coherently, and could the language extend to new materials? These questions connect examples you like with your own needs. Distinguishing what a published presentation shows from what requires further explanation makes the review more useful and avoids assumptions about outcomes or delivery.

Quick answer

Review corporate identity projects through the relationships between logo, typography, colour and layout across applications. An attractive presentation alone does not prove production or business outcomes. Examine content density, small uses and template logic. Ask the design team about goals, delivery scope and conditions not described in the portfolio rather than inferring them from the images.

Identify what the project page describes

A project labelled logo design differs from one labelled logo and corporate identity. In BOCW's published portfolio, Soffany and Solstage appear under logo and corporate identity; Arvena also lists packaging, and Navtel also lists a website. These descriptions help distinguish project types.

A category does not establish undisclosed goals, client outcomes or production details. Keep separate notes for what the presentation visibly shows and what you still want to learn. This makes portfolio evidence useful without expecting it to answer questions the page does not address.

Read connections rather than isolated visuals

Review several applications of the same brand together. Which elements connect them beyond the logo? Heading structures, photography, spacing and supporting graphics may establish a shared language. Repeating the mark on every surface does not demonstrate the depth of the system by itself.

Flexibility also matters. A product image and a long information page need different arrangements. If priorities can change while the visual relationship remains clear, the identity may support a broader range of uses. Identical compositions are only one possible approach to consistency.

Compare ideal presentation content with your own

Portfolio layouts are often selected to communicate a design idea clearly. Your text may be longer, product range wider or contact details denser. Consider how the direction would handle that information. Ask whether the space shown in the presentation can survive ordinary use.

Imagine a hypothetical furniture brand whose catalogue requires dimensions, materials and variations alongside photographs. For that business, the organisation of dense pages matters as much as elegant covers. A reference becomes useful when its strengths are connected to the content your team actually needs to publish.

Separate visual presentation from production evidence

An image of a sign or package does not establish that it was produced at full size. Review any stated production information, and avoid a definite conclusion when none is given. A design proposal can still be valuable; be clear about what it demonstrates.

Discuss materials, application methods and conditions separately for your project. Ask for a relevant example where available. The goal is not to demand every technical detail from a portfolio page, but to understand when the conditions affecting your decision will be checked.

Write a brief evidence note for each reference

Answer the same questions for every project you like. This turns a loose inspiration board into a useful assessment file and helps explain your interests during a discussion with the designer.

  • Visible applications: which surfaces does the presentation show?
  • Shared language: what connects them beyond the logo?
  • Relevant need: which of my project's usage questions does it address?
  • Missing information: which goal, delivery detail or production condition needs clarification?
  • Original direction: which approach do I want to explore without copying the reference?

Use references to frame questions, not copies

Requesting the same colours and composition can transfer another brand's solution without testing your own needs. Describe the useful quality instead: calm information organisation, flexible headings or a visual structure linking products. The reference then becomes an input for original design.

When exploring BOCW's portfolio, focus on these relationships alongside project names. Share relevant examples and explain why they matter. That allows a new project to be assessed around your brand conditions instead of treating an existing visual treatment as a ready-made answer.

Key takeaways

  • Distinguish project labels, visible applications and undisclosed details.
  • Evaluate shared visual rules rather than logo repetition alone.
  • Extract approaches to investigate from references instead of forms to copy.

Frequently asked questions

Were all applications in the portfolio delivered?

Do not assume that from imagery alone. A page may illustrate a design idea or representative uses. Ask the studio for clarification when delivery scope matters to your decision. A presentation and a file handover provide different kinds of information.

Must I choose examples from my own industry?

No. Shared problems such as dense content, bilingual communication or small surfaces appear across industries. Assess sector similarity alongside usage similarity to create a broader, more relevant reference list for the project.

How should I explain a project I like?

Identify the useful quality and why it matters, such as product-family organisation or legible headings. Discuss how a similar problem could be solved for your content rather than asking for the same appearance. This gives the designer a clearer starting question.