Bring different skills into the same project

Knowledge handover in long client relationships

Bring different skills into the same project
OXOAK / Content and design

Practical notes

1 min read

Knowledge handover in long client relationships

Maintain a glossary, account ownership and decision history. Verify a handover through a real update task rather than treating a shared folder as proof of continuity.

Bring different skills into the same project

Putting evidence and responsibility into practice

Public communication should distinguish goals, actions and evidenced results. People, clients, recognition and environmental statements require support; imagery alone is not evidence.

Bring different skills into the same project

Checking the result

Check names, dates, permissions and numerical sources and retain a correction route. Withhold unconfirmed facts while explaining methods and scope concretely.

Bring different skills into the same project
Bring different skills into the same project

Related practical notes

Change approval

Change approval

Project discipline

Define change approval responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.

Component maintenance

Component maintenance

Project discipline

Define component maintenance responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.

Customer journeys

Customer journeys

Project discipline

Define customer journeys responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.

Search experience

Project discipline

Define search experience responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.

Service blueprints

Service blueprints

Project discipline

Define service blueprints responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.

Usability observation

Usability observation

Project discipline

Define usability observation responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.

Why UX is not optional

Practical notes

Why UX is not optional

Define audience tasks and current difficulties at kickoff and test journeys early. Scale research to the budget without omitting the problem definition.

Why UX is not optional
OXOAK / Editorial

Practical notes

Practical notes

Demystifying UX and industry terminology

Practical notes

Demystifying UX and industry terminology

Explain journeys, wireframes and prototypes through problems, structure and interaction testing. Use one shared page example so the team does not work from conflicting definitions.

Demystifying UX and industry terminology
OXOAK / Editorial

Practical notes

Practical notes

UX: The art and science of problem solving

Practical notes

UX: The art and science of problem solving

Record goals, journeys and hesitation before proposing testable changes. Ground decisions in observation rather than internal taste alone.

UX: The art and science of problem solving
OXOAK / Editorial

Practical notes

Practical notes

Practical notes

How understanding human mental models drives better UX design

Ask participants to group content and explain labels, then compare with navigation. Internal departments may not match how customers understand services.

How understanding human mental models drives better UX design
OXOAK / Editorial

Practical notes

Practical notes

Defining an expanded UX service

Practical notes

Defining an expanded UX service

Separate research, structure, prototypes and testing into deliverables and explain client participation. Do not label a design discussion as completed research.

Defining an expanded UX service
OXOAK / Editorial

Practical notes

Practical notes

Defining outcomes in an education partnership

Practical notes

Defining outcomes in an education partnership

State questions, student responsibilities, deliverables and publication permissions. Keep unconfirmed partnerships as plans rather than public credentials.

Defining outcomes in an education partnership
OXOAK / Editorial

Practical notes

Practical notes

Will AI destroy the art of human communication?

Practical notes

Will AI destroy the art of human communication?

Use tools for notes and drafts and review facts, tone and commitments before sending. Check permission for personal accounts and sensitive information.

Will AI destroy the art of human communication?
OXOAK / Editorial

Practical notes

Practical notes

Accessibility design in practice

Practical notes

Accessibility design in practice

Specify focus states, error messages and image-description responsibilities beside components. Review a complete keyboard journey as well as static frames.

Accessibility design in practice
OXOAK / Editorial

Practical notes

Practical notes

Connecting service touchpoints and operations

Practical notes

Connecting service touchpoints and operations

Map enquiry, confirmation and delivery. Name the owner and handover material at each touchpoint, then check whether customers can see progress while waiting.

Connecting service touchpoints and operations
OXOAK / Editorial

Practical notes

Practical notes

How to create a digital strategy roadmap

Practical notes

How to create a digital strategy roadmap

Separate current problems, near-term improvements and later experiments, with owners and evidence. Keep the rationale for roadmap changes traceable.

How to create a digital strategy roadmap
OXOAK / Editorial

Practical notes

Practical notes

7 tips for a successful digital roadmap

Practical notes

7 tips for a successful digital roadmap

Give each initiative a user problem, owner, dependencies and acceptance criteria. Plan verifiable stages rather than committing every future idea at once.

7 tips for a successful digital roadmap
OXOAK / Editorial

Practical notes

Practical notes

Digital product design workbook

Download this editable digital product design workbook to record current work, open questions and owners. OXOAK examples can be adapted to the project.

UX v SEO: Friends or Foes?

Practical notes

UX v SEO: Friends or Foes?

Use headings for customer questions, direct answers and clear onward navigation. Avoid keyword-only pages and excessive simplification.

UX v SEO: Friends or Foes?
OXOAK / Editorial

Practical notes

Practical notes

Design Fidelity & Prototyping

Practical notes

Design Fidelity & Prototyping

Use low-fidelity wireframes for information order and realistic content for reading and brand questions. Avoid polishing every shadow before the structure has been validated.

Design Fidelity & Prototyping
OXOAK / Editorial

Practical notes

Practical notes