What this is

Dakic already had a Projects page for ActionAmp, Workomator, Sidian Sidekicks, and MindUpload. Adding technical fixes and product decisions to that page would have changed a clear portfolio into a mixed archive.

We created a separate Work library, linked from the footer and organized around five kinds of evidence.

The friction

A studio portfolio answers one question: which products has this team created? The answer gets harder to scan when the page also collects codebase repairs, research notes, client engagements, and small tools.

Calling the combined collection Case Studies would create another problem. Some entries describe a product decision or an owned experiment. They do not have a client, engagement, and business outcome. The label would promise evidence the entry could not supply.

The main navigation already carried the destinations a buyer needs first. Another item would make the site harder to scan before the library had enough material to justify that prominence.

The senior decision

We kept Projects intact and created Work as a broader evidence library.

Projects presents studio products as products. Work explains a useful change, the decision behind it, and the evidence a visitor can inspect. A studio product can appear in both places because the pages serve different reading goals.

We used Work instead of Case Studies. The name can hold approved client work, tools, experiments, systems, fixes, and research without forcing each artifact into a client story.

The link lives in the footer. That placement makes the library available without adding another choice to the primary navigation.

What became real

The site now has a /work index, category definitions, a reusable detail-page template, and a content collection with fields for status, evidence, role, timeframe, and relevant services.

The first published items examine AI-assisted work. Product-decision entries can use the richer Work format with screenshots, status labels, and evidence blocks.

Evidence

The Projects page still presents the studio portfolio. The Work page presents the new editorial and evidence layer. Projects remains in the company links, while Work appears beside it in the footer.

What we learned

Navigation labels set an expectation. A visitor should know whether a link leads to products, client outcomes, or technical writing before opening it.

Two pages can discuss the same product without duplicating each other. One shows the product. The other examines the judgment that shaped it.

Current state

The information architecture and content model are live. The library will gain categories as new evidence-backed entries are published.