Selected project artwork
Sey Circular Biosphere
An island scene held inside a circular form. Nature, place and purpose become one visual starting point.
See the website storyNexney / The creative portfolio
Website & platform storiesFrom a mark.
To a whole experience.
Your business has a character. Let it come through in the places people meet it: a logo, a building, a proposal—and the way the work gets done.
Selected identity artwork, new application concepts and original systems studies. Explore the detail behind each idea.
01 / Identity & material
A familiar shape.
A different expression.
Colour, finish and context change how a mark feels. These studies begin with retained project artwork, then explore how an identity can grow into a wider visual language.
Selected project artwork
Sustainable Tech
A bold green mark with water and leaf details. The identity gives product material a consistent point of recognition.
See the product imagery study02 / Brand applications
Picture your brand
out in the world.
Recognition comes from carrying the same idea across different surfaces. One identity, considered at three very different scales.
New Nexney concepts, visualised with AI assistance. These depict possible applications, not existing premises, vehicles or manufactured garments.
01 / Dimensional signage
Make an entrance.
A mark changes when light, scale and materials become part of it. This study carries the Nexney identity onto a building, with space around the lettering and a quieter supporting line.
02 / Vehicle livery
Recognisable on the move.
One strong mark, a clear colour division and room to breathe. The same identity becomes a moving introduction, designed to be understood at a glance.
03 / Office wear
Part of the everyday.
On clothing, restraint matters. Smaller placement and a simple palette carry the brand without overwhelming the person wearing it. Production artwork would be prepared for the chosen print method.
Imagine the same care applied to your own identity.
Discuss your brand material03 / Documents with purpose
The next impression
could be a document.
A proposal should help someone decide. A brief should help them explain. A report should help them see what changed. The layout follows the job the document needs to do.
Three Nexney template studies. Each uses illustrative sample content; download the editable Word version or inspect the finished PDF.
2 pages / SampleProject proposal
A proposal with a point.
Make the opportunity, scope and next decision easy to find. A considered opening followed by practical project detail.
2 pages / SampleProject brief
Space for the right questions.
Turn a loose idea into a useful conversation. A working document for goals, audience, materials and the decisions still to make.
1 page / SampleProgress report
Progress you can understand.
Show what moved forward, what needs a decision and what happens next. A concise report built for an ongoing working relationship.
From the project archive
A company profile.
A clearer introduction.
Stravon’s editorial study brings service information into a more considered reading order, using the supplied identity. This is a reconstructed portfolio excerpt.
Explore the Stravon storySystems design / Three illustrative studies
See the thinking
behind the screen.
Your system needs to carry the right information to the right person, with a clear next step when something changes.
Explore three original design examples: the data they keep, the decisions people make and the details that make a workflow dependable.
Illustrative architecture. All scenarios, records and roles below are fictional. These are design studies, not diagrams of a deployed client system.
Evidence → review → approved recordCan you trust what the screen tells you?
A document arrives. Someone extracts the useful details. Then a correction comes in. Your team needs to know which information is current and why it can be trusted.
Design intentionA record with a route back to its evidence.
- 01Source material
Keep the source
Retain the original note and identify its revision.
Carry forwardSource + revision + received date - 02Working context
Prepare a draft
Propose useful details with a reference to the exact passage.
Carry forwardProposed value + evidence reference - 03Human decision
Review the meaning
A reviewer checks the source, resolves ambiguity and approves this version.
Carry forwardDecision + reviewer role + reason - 04Retained outcome
Release a record
Make the approved version available while keeping its history.
Carry forwardApproved snapshot + source link
When the expected path breaksThe source changes after review
Create a new draft and request another review. Keep the last approved record clearly labelled until its replacement is approved.
Follow one fictional exampleSample E-14
A changed workshop time
Revision 2 approved
- Original evidence
- Note revision 1: “The workshop starts at 09:00.”
- New evidence
- Note revision 2, paragraph 3: “The start time is now 09:30.”
- Review decision
- Reviewer confirms the correction applies to the same workshop.
- Released value
- 09:30, linked to revision 2 and its approval.
Both source versions remain available to the reviewer. The new value does not erase the reason for the change.
The decisions beneath the diagram
Provenance
A value carries its evidence.
The proposed time stays attached to the source revision and passage. A polished summary alone does not establish that a fact is correct.
Human decision
Approval belongs to a version.
A reviewer approves the specific draft they inspected. If the source changes during review, the decision pauses until they see the new version.
Retry and recovery
An unreadable file stays unresolved.
Retain the source and retry the same work item. A second attempt must not create a second approved record or silently guess a missing value.
Look closer: access, history and tradeoffs
Who can do what?
- Contributor
- Supply evidence and see the status of their submission.
- Reviewer
- Inspect sources, resolve differences and approve a revision.
- Reader
- Use approved information within their permitted scope.
A useful history
Record the source revision, proposed change, reviewer role, decision time and reason. Preserve previous approvals.
The tradeoff
Versioned review adds a human step and a queue to manage. It is useful when an incorrect published detail would cost more than the time spent checking it.
Built to change with the business.
If a second approval becomes necessary, introduce it at the decision point and migrate open work deliberately. Keep the evidence and previous decisions intact.
Observe.
Improve.
Request → approval → fulfilmentWho owns the next step?
A request is discussed in one place, approved in another and delivered by someone else. You should be able to see what was agreed, who is responsible and what is still waiting.
Design intentionA handover with context, responsibility and a receipt.
- 01Source material
Capture the request
Give one request a reference, an owner and the details needed to act.
Carry forwardRequest + scope + supporting material - 02Working context
Check what is needed
Identify missing information and prepare a clear proposed action.
Carry forwardRequirements + cost estimate + due date - 03Human decision
Approve the scope
The responsible person accepts, declines or returns the proposal.
Carry forwardApproved version + limits + decision - 04Retained outcome
Deliver and confirm
Assign the approved work and retain evidence that it was completed.
Carry forwardWork reference + owner + completion receipt
When the expected path breaksA delivery update never arrives
Mark the outcome as unconfirmed, check the existing work reference and ask its owner. A timeout must not trigger a duplicate order.
Follow one fictional exampleSample R-08
One replacement sign
Waiting for approval
- Requested
- Replace one damaged reception sign using the supplied artwork.
- Prepared
- Size, artwork revision, supplier estimate and requested date are together.
- Decision needed
- Budget owner accepts this scope and estimate, or requests changes.
- Next permitted step
- Assign fulfilment only after approval of the current version.
If the quantity changes, the proposal returns for review. A previous approval cannot authorise a larger request.
The decisions beneath the diagram
Data relationships
One request, related decisions.
Keep the request, its revisions, approvals and fulfilment receipt connected. People can find the full context without copying it into every handover.
Human decision
Approval has a boundary.
The approver accepts an explicit scope and limit. A material change to quantity, cost or specification creates a new decision, rather than borrowing an old one.
Retry and recovery
A second click is the same request.
Repeated submissions resolve to the existing work reference. Failed notifications can be retried; ordering or delivery needs its own confirmed receipt.
Look closer: access, history and tradeoffs
Who can do what?
- Requester
- Create a request and follow their own work.
- Approver
- Decide within their assigned responsibility and limits.
- Fulfilment owner
- Act on approved work and record its outcome.
A useful history
Keep each scope revision, state change, responsible role and reason. Completion evidence is a separate event from approval.
The tradeoff
Clear stages reduce uncertain handovers, but too many approvals can slow ordinary work. Start with the decisions that matter and make exceptions visible.
Built to change with the business.
As the team grows, responsibility may move from one person to several departments. Redesign routing and access together, while existing requests retain an accountable owner.
Observe.
Improve.
Campaign → qualified enquiry → learningWhat actually led to a useful conversation?
A campaign gets attention. A few people enquire. The valuable question is which message helped the right person understand your offer, and what you should improve next.
Design intentionA connection between creative work and an honest next decision.
- 01Source material
Identify the message
Give the offer and each creative version a distinct reference.
Carry forwardCampaign + creative + intended audience - 02Working context
Retain enquiry context
Carry a known campaign reference into the enquiry when available.
Carry forwardEnquiry + source reference + unknowns - 03Human decision
Qualify the conversation
A person checks fit and records what the customer actually needs.
Carry forwardHuman assessment + next step + reason - 04Retained outcome
Learn from the outcome
Compare observed outcomes and choose the next change to test.
Carry forwardRecorded outcome + limits + next hypothesis
When the expected path breaksThe source reference is missing
Keep the enquiry and label its source unknown. Ask when useful, preserve any self-reported answer separately and avoid assigning credit by guesswork.
Follow one fictional exampleSample C-03
A clearer website offer
Illustrative trace
- Creative reference
- Version B: a message about making services easier to understand.
- Enquiry context
- A known source reference accompanies a request about a service website.
- Human assessment
- A conversation establishes the scope; a quotation is requested.
- Learning
- Explore this message again. A requested quotation is not yet a paid job.
This is an invented example, not a campaign result. No visitor, enquiry or revenue data is represented here.
The decisions beneath the diagram
Provenance
Observed and reported stay distinct.
Store an observed source reference separately from what a person says influenced them. An unknown source remains unknown; one link does not prove causation.
Human decision
A person decides whether it is a fit.
An enquiry is an expression of interest. Qualification, quotation and a paid project are different outcomes with their own evidence and decision dates.
Retry and recovery
A retry does not become another lead.
Repeated form delivery links back to the same accepted enquiry. Reporting can be rebuilt from recorded events without counting the same conversation twice.
Look closer: access, history and tradeoffs
Who can do what?
- Campaign editor
- Manage creative references and see aggregate outcomes.
- Enquiry owner
- Read the brief and record agreed next steps.
- Business owner
- Review appropriate outcomes and decide what to test next.
A useful history
Record changes to qualification and outcome with a responsible role and date. A project enquiry does not create permission to send marketing.
The tradeoff
Less individual tracking means some journeys stay incomplete. Use aggregate signals and voluntary conversation context, and describe those limits when making decisions.
Built to change with the business.
When the offer or audience changes, update the questions and outcome definitions. Preserve the old definitions so yesterday’s results are not silently reinterpreted.
Observe.
Improve.
Opening these studies sends no request and saves no data. The diagrams explain design choices; they do not run a connected service.
The work continues
Now see the ideas
become digital experiences.
Explore the websites, platforms, films and character work that bring the wider portfolio together.
Explore website & platform stories