The Lucky Way

This page outlines how we run projects at Lucky Media, from the first client conversation to handing off a finished product.

Our process has four stages:

1. Getting to know the client
2. Product, purpose, and research
3. Design
4. Development and testing

Getting to Know the Client

The management and design team meets with the client to understand what they need. We take notes and put together a mood board to align on direction. Technical questions are addressed early to avoid surprises later.

The design team maps out the site structure and workflow. We pull information from emails, documents, and meetings to build a full picture of the project scope. This helps with resource planning and setting realistic timelines.

Product, Purpose, and Research

With a clear understanding of the client’s goals, the UI/UX team defines what the product needs to do and who it is for. We look at the target audience, core requirements, and objectives to design an experience that works for real users.

Research into user pain points, preferences, and behaviors informs interface decisions. The team balances aesthetics and functionality to produce something that is both usable and visually solid.

Design

Once the client approves the technical scope and process, we ask them to provide relevant content: logos, descriptions, images, color styles, and any other brand materials.

The UI/UX team follows four steps:

1. Wireframing
2. Initial Design
3. Feedback and Adaptation
4. Isnification

Short version: We wireframe the structure and get client feedback. We build the initial design on top of the wireframe. We refine based on feedback. Then we prepare the design for development in a step we call Isnification.

1. Wireframing

We start with the Figma Web UI Starter and build the wireframe from there. Components, margins, padding, border radius, and fonts are all defined at this stage. Once the wireframe is done, we share it with the client via Figma and collect feedback before moving forward.

2. Initial Design

We take the wireframe and turn it into a full visual design. Colors, components, and typography are applied based on client preferences and the nature of the project. The client can leave comments directly in the Figma project as we iterate through each section.

3. Feedback and Adaptation

We incorporate the client’s actual content into the design and adjust based on their approvals and feedback. This step ensures the final design matches what the client actually needs.

4. Isnification

Isnification is our internal term for preparing the design for development. Once the desktop design is approved, we adapt it for mobile screens and clean up components. Images, SVG logos, fonts, and colors are exported in the formats developers need.

The word “Isnification” comes from Art, our first designer (yes, his name is Art), who worked closely with our developer Isni. The name stuck.

Development and Testing

The design and development teams meet to go over project details, agree on the tech stack, and align on the handoff process. Designers stay available to answer questions throughout development.

When the build is close to done, we move to the staging phase. We run through our checklist, log any issues in the GitHub repository, and do an internal review. The project is then presented to the client for final review.