Solution First: Why We Start With the Problem, Not the Screen

Most digital projects begin with colours, layouts and technology. At CreativeIyke, we begin with a simpler question: what problem are we actually trying to solve? Discover why a Solution First approach leads to better digital products.

There is a temptation in the digital industry to start with the thing that is easiest to see. A client wants a new website, so the conversation starts with pages, colours and layouts. A business wants an app, so the discussion immediately moves towards features and technology. Someone wants to introduce AI, and suddenly everyone is asking which model, API or framework should be used. These conversations are understandable, but they can put the cart before the horse. At CreativeIyke, we believe the first question should be much simpler: what problem are we actually trying to solve?

That question is the foundation of what we call Solution First. It is not a slogan we use to make our services sound different, and it is certainly not a clever way of saying that we do design and development. It is a way of thinking about digital products before we decide what to design, what to build or which technology to use. We look at the business objective, the people using the service, the existing systems, the operational reality and the opportunities for improvement, then work towards the solution that makes the most sense.

Sometimes that solution is a new website. Sometimes it is a redesign of an existing product. It might be a customer portal, a SaaS platform, a mobile application, a service redesign, an AI-powered workflow or a combination of several technologies. And occasionally, the best solution is not to build anything at all. That last one is important. Good digital strategy is not about finding reasons to build more software. It is about making better decisions about where technology, design and human needs intersect.

Solution First Starts With the Problem

A digital project can begin with an apparently straightforward request: "We need a new website." But that statement tells us very little about the actual problem. Perhaps the website is generating traffic but very few enquiries. Perhaps customers cannot find the information they need. Perhaps internal teams are spending hours answering questions that could be handled through self-service. Perhaps the organisation has grown and its current platform can no longer support its operations. Or perhaps the website looks dated and the brand no longer represents where the business is going.

These are very different problems, even though they can all arrive disguised as a request for "a new website". If we accept the requested solution without investigating the underlying issue, there is a real possibility of producing something that looks better without actually making the business better. The new website might have beautiful pages, impressive animations and a polished visual identity, yet the conversion problem remains, the internal workflow is still manual and customers continue to struggle.

That is why our first stage is Discovery & Audit. We look at the problem, the existing product, the user experience and the technical landscape before moving into design and development. We consider stakeholder goals, user needs, technical feasibility, architecture, risks and constraints so that the project begins with a clearer understanding of what needs to change. It is a relatively simple principle, but it prevents an enormous amount of wasted effort further down the line.

WHAT PROBLEM ARE WE SOLVING?

Goals • Revenue • Efficiency • Growth

Users • Customers • Staff • Accessibility

Journeys • Processes • Content • Operations

Systems • Data • APIs • Infrastructure

Automation • AI • Innovation • Differentiation

Caption: Solution First brings business, people, service, technology and opportunity into the same conversation before decisions are made.

We Don't Start With the Screen

One of the biggest differences between a Solution First approach and a conventional design process is what happens before the first interface is designed. We don't believe the first deliverable should always be a homepage concept. A screen can only show part of the problem. Before deciding what a user interface should contain, we need to understand what the user is trying to accomplish and what the organisation needs to make that possible.

This becomes particularly important when we work on complex digital products. A dashboard might appear to be a straightforward collection of charts and controls, but behind it could be authentication, user permissions, databases, APIs, financial information, third-party integrations and business rules. Designing the dashboard without understanding those underlying requirements could produce an attractive interface that does not reflect how the system actually needs to operate.

The same applies to service design. A government or healthcare service might have a website as its most visible touchpoint, but the user's journey can extend across forms, call centres, appointments, internal teams, policies and multiple technical systems. In those environments, redesigning the website without examining the wider service can simply move the problem around. The interface changes, but the experience does not fundamentally improve.

Design Is Part of the Solution, Not the Whole Solution

We are a design-led company, so this might sound slightly strange coming from us, but design on its own is not enough. A beautiful interface cannot compensate for a broken business process, a poorly structured database, an unreliable integration or a service that fundamentally misunderstands what users need. Equally, technically excellent software can fail because people cannot understand it, do not trust it or simply do not want to use it.

This is why CreativeIyke brings Human-Centred UX/UI Design and Custom Web & Mobile Engineering together. We want the experience and the technology to inform each other throughout the project. User journeys influence technical decisions, while technical constraints and opportunities influence the experience we design. Instead of throwing a design over a wall to a development team and hoping everything survives the journey, we work towards a connected product where design, engineering and business objectives are considered together.

The result is not necessarily more complicated. In fact, the opposite can happen. When the underlying problem is understood properly, unnecessary features can be removed, workflows can become simpler and technology can be used more intelligently. The goal is not to create something that looks sophisticated. The goal is to create something that works.

The Four Stages Behind Solution First

Our Solution First approach is structured around four connected stages: Discover, Architect, Build and Optimise. They are not rigid boxes that prevent a project from evolving. Instead, they provide a framework for making better decisions at the right time. Each stage answers a different question, and together they create a pathway from an unclear problem to a working digital product that can continue to improve.

End-to-End Strategic Delivery Engine

Understand the problem, users, existing systems, technical landscape and constraints.

Define user journeys, information architecture, system architecture, interfaces and integrations.

Bring the frontend, backend, infrastructure, integrations and product experience together.

Measure, test, learn and continuously improve the product after launch.

Caption: A digital product should not stop evolving when it goes live. Solution First connects strategy, design, engineering and optimisation into one continuous cycle.

01. Discover: Understand Before You Commit

Discovery is where assumptions get challenged. We examine the existing product, service or business process and try to understand what is actually happening rather than relying entirely on what we think is happening. That can involve stakeholder discussions, UX research, content audits, technical reviews, competitor analysis, analytics and examination of existing systems, depending on the nature of the project.

The objective is not to produce a large document that sits in a folder and is forgotten once development starts. Discovery should produce decisions. We want to identify the most important problems, understand their impact, establish constraints and determine what needs to happen next. If a particular feature does not contribute to the business objective or user need, we should be able to question whether it belongs in the product at all.

For a business investing significant money into a digital product, this stage can be one of the most valuable parts of the entire engagement. Spending more time understanding the problem at the beginning can prevent expensive changes later. It is the digital equivalent of checking the foundations before deciding how many floors to put on the building.

02. Architect: Design the Experience and the System

Once the problem is understood, we can start defining what the solution should actually look like. This is where UX strategy, user journeys, information architecture, wireframes, interface design and technical architecture begin to converge. We are not simply designing screens. We are designing how the product works.

At this stage, we consider the different people who will use the product, the tasks they need to complete and the information they need at each point in their journey. We also think about what happens behind those interactions. Which data needs to be stored? Which systems need to communicate? What permissions are required? Where can automation remove unnecessary work? How should the product behave when something goes wrong?

This is also where a design system becomes valuable. Instead of treating every screen as a separate creative exercise, we establish reusable components, patterns and rules that allow the product to remain consistent as it grows. Good architecture, whether visual or technical, creates room for the future without turning every future change into a rebuild.

Symmetrical Experience & Infrastructure Synthesis

Caption: The experience users see and the systems they don't should be designed as parts of the same product.

03. Build: Turn the Strategy Into Something Real

This is where ideas meet reality. Designs become interfaces, databases are implemented, APIs are connected and the product starts to behave like the system it was always intended to become. Our approach brings frontend and backend development together so that the experience is not separated from the technology supporting it.

We build with scalability, maintainability and performance in mind because a product should not become impossible to manage six months after launch. Depending on the project, this might involve modern web technologies, cloud infrastructure, third-party integrations, authentication systems, payment services, AI capabilities, analytics or other components required to make the product work.

AI has also changed what is possible during this stage. We increasingly use AI-assisted development and intelligent integrations where they provide genuine value, but Solution First means we do not use AI simply because it is fashionable. The question is always what the technology contributes to the product. If AI can reduce manual work, improve personalisation, automate a repetitive process or create a capability that would otherwise be impractical, it becomes interesting. If it simply adds a chatbot to a website because everyone else has one, we would question the value.

04. Optimise: Launch Is Not the Finish Line

A product can be technically complete and still have enormous room for improvement. Once real users begin interacting with it, new information becomes available. We can see where people struggle, which features are used, where journeys are abandoned and how the product performs under real conditions. That information should influence what happens next.

Our optimisation stage brings together performance monitoring, analytics, user feedback, security verification and ongoing iteration. We look for opportunities to remove friction, improve performance, strengthen accessibility and increase the value the product creates for both users and the organisation. A product that learns from its users can become significantly better than the product that was originally imagined during the planning stage.

This is especially important for businesses that are scaling. The needs of a company with 100 customers may look very different from those of a company with 10,000 customers. The same applies to public services, SaaS platforms and digital products operating across multiple teams. Optimisation ensures that the product evolves instead of becoming another piece of legacy technology that eventually needs to be replaced.

Solution First Does Not Mean Technology Last

There is an important distinction here. Saying that we put the solution first does not mean that technology is an afterthought. Quite the opposite. Technology needs to be involved early because technical decisions can fundamentally influence what is possible, what it will cost and how well the solution will scale.

If a business wants to build a customer platform, for example, we need to understand the existing systems, data structures and integrations before promising a particular experience. If a healthcare organisation needs a digital service, privacy, accessibility and security considerations need to influence the architecture from the beginning. If a fintech company wants an application involving payments or open banking, regulatory and technical considerations cannot simply be added at the end of the design process.

Solution First therefore means technology in context. We use technology because it helps solve a problem, not because the technology itself is the project. The distinction might sound subtle, but it changes how decisions are made.

Where AI Fits Into the Solution First Approach

AI deserves particular attention because it has changed the expectations around digital product development. Businesses can now prototype ideas, generate content, automate workflows and build software considerably faster than before. That is exciting, but speed can also create a new problem: building the wrong thing faster.

A business can spend less time and money creating an AI-powered product while still ending up with a product nobody needs. It can automate a process that should have been redesigned first. It can introduce an AI assistant where a simple interface would have been clearer. It can generate a sophisticated prototype without considering data quality, security, accuracy or what happens when the AI gets something wrong.

Our Intelligent AI Integrations capability therefore sits within the wider Solution First philosophy. We look for areas where AI can produce measurable value, whether that means intelligent automation, conversational interfaces, data analysis, workflow assistance or other capabilities. The technology is exciting, but the outcome matters more.

Value-Driven Technology Decision Tree

Caption: AI should be selected because it improves the solution, not because adding AI makes the product sound innovative.

Solution First Is Also About Knowing What Not to Build

Perhaps one of the most valuable outcomes of this approach is knowing when to stop. Digital projects can accumulate features remarkably quickly. Someone suggests a dashboard, another person wants notifications, another wants an AI assistant, someone else wants a mobile app and suddenly the original problem has disappeared beneath a mountain of functionality.

Feature quantity is not the same thing as product value. Every additional feature introduces design decisions, development effort, testing requirements, maintenance costs and potentially new security or accessibility considerations. A product with twenty well-designed capabilities that solve genuine problems can be considerably more valuable than one with sixty features that users barely understand.

Solution First gives us a framework for challenging those decisions. Does this feature solve a meaningful user problem? Does it support the business objective? Is there evidence that people need it? Can the existing product already achieve the same outcome? What happens if we don't build it? These questions are not intended to make projects smaller for the sake of being smaller. They help ensure that the investment goes towards the things that matter.

From Brand to Product: Why CreativeIyke Brings Different Disciplines Together

CreativeIyke has evolved beyond the traditional definition of a web design agency. Our work sits at the intersection of Branding & Visual Strategy, Human-Centred UX/UI Design, Custom Web & Mobile Engineering and Intelligent AI Integrations. That combination allows us to look at digital products from several perspectives without treating them as disconnected disciplines.

Brand determines how an organisation is perceived. UX determines how people move through the experience. Service design considers the wider journey across people, processes and systems. Engineering turns those ideas into functioning technology. AI can introduce new capabilities and automation where it genuinely adds value. When these disciplines work together, the result can be more coherent than simply passing a project between separate suppliers.

That does not mean every project requires every capability. A company might need a brand identity before it needs software. Another might have a strong brand but need a new SaaS platform. A public-sector organisation might need service design and accessibility work without requiring a completely new technical platform. Solution First means understanding which combination is appropriate rather than selling the same package to everyone.

Who Is Solution First For?

Solution First is particularly useful when a digital problem does not fit neatly into one category. Perhaps the organisation has a website problem that is actually a service problem. Perhaps an operational problem is really an automation opportunity. Perhaps a customer-experience problem is being caused by outdated technology. Perhaps a business has an idea for an application but has not yet worked out what the product should actually do.

It is also valuable for organisations that are growing. As businesses move from early-stage operations into more complex environments, the digital infrastructure supporting them needs to evolve. Websites become platforms, spreadsheets become systems, manual processes become workflows and individual tools begin to need integration. The decisions made at those transition points can have a significant effect on how efficiently the organisation scales.

For public-sector and healthcare organisations, the same thinking applies but with an additional layer of responsibility. The service needs to work for a diverse population, meet accessibility requirements and operate within organisational, regulatory and technical constraints. A polished interface is useful, but it is only one component of a successful service.

The CreativeIyke Difference Is Not That We Design or Develop

There are plenty of companies that design websites. There are plenty that build applications. There are agencies offering branding, UX, software development, AI integration and almost every other digital service imaginable. Simply listing those capabilities does not create a meaningful difference.

For us, the difference is in how those capabilities are connected. We don't want to be the team that receives a predetermined solution and simply executes it. We want to understand why the solution is being proposed, what outcome it is supposed to create and whether there is a better way to achieve that outcome.

That is what Solution First means at CreativeIyke. It means questioning the brief when necessary. It means understanding users before designing screens. It means considering technology before promising functionality. It means using AI where it creates genuine value. It means thinking about accessibility before launch rather than after. And it means measuring what happens once the product is in the real world.

From Problem to Product

A good digital product rarely appears fully formed. It starts with a problem, a frustration, an opportunity or an ambition. The job is to understand that starting point properly, identify what is worth solving, design a sensible experience around it and build the technology required to make it real.

That is the journey we have built CreativeIyke around: Discover → Architect → Build → Optimise. We begin by understanding the problem and the environment around it. We then architect the experience and technology, build the product with the appropriate tools and disciplines, and continue optimising once real people start using it.

The result might be a website, a web application, a SaaS platform, a service redesign, an AI-powered workflow or something that does not fit neatly into any of those categories. The label matters less than the outcome. What matters is that the digital solution makes something clearer, simpler, faster, more accessible, more efficient or more valuable.

That is what we mean by Solution First.

Continuous Closed-Loop Strategic Product Lifecycle

Understand the problem

Design the right solution

Make it real

Learn and improve (↻ loop to DISCOVER)

Caption: A continuous, iterative framework connecting human empathy, commercial strategy, technical precision, and artificial intelligence into unified digital products.

What Solution First Means in Practice

Comparative Operational Philosophy

Caption: Solution First changes the conversation from what should we build? to what should improve?

A Better Question to Start With

The next time your organisation says, "We need a new website", perhaps don't open Figma immediately. Ask why. What has changed? What are customers struggling with? What are employees doing manually? Which parts of the service create friction? What happens before someone reaches the website, and what happens after they leave? Which systems are involved? What would success actually look like six or twelve months after launch?

The answers might lead to a website. They might lead somewhere else entirely. And that is precisely the point.

At CreativeIyke, we believe the strongest digital products are not defined by the technology used to build them or the number of features they contain. They are defined by the problems they solve and the value they create for the people and organisations that rely on them.

Don't start with the screen. Start with the problem.

Start Solution First.

Ready to solve the right problem?

If you are planning a new digital product, redesigning an existing platform or trying to work out what technology your business actually needs, CreativeIyke can help you move from uncertainty to a clear, buildable solution.

Iyke Anselm

UX/UI designer and developer in Birmingham, UK. I design and build digital products for SaaS, fintech and public sector teams.