Andrew Crossley
    ABOUT ANDREW CROSSLEY

    I did not plan to become a Product Manager

    I simply could not stop looking for better ways to do things.

    • I have always noticed the unnecessary steps.
    • The repetitive task that should have been automated.
    • The form asking a customer to enter the same information twice.
    • The process that required ten clicks when it could have taken three.
    • The recurring customer problem that everyone had learned to accept.

    Long before I understood what product management was, I was already thinking about every click, every input, every delay, every frustration and every possible solution.

    That way of thinking eventually became my career.

    WHERE IT STARTED

    My career started with customers, not products

    I began my career in sales, working with companies including Just Eat, Sage and Echo U.

    That experience taught me how customers really behave.

    I learned what makes someone pay attention, what makes them trust a business, what creates objections and what ultimately makes them say yes or walk away.

    It also taught me that customers rarely care about features in isolation.

    They care about whether something saves them time, reduces their costs, removes frustration or helps them achieve a result.

    Those conversations became the foundation of how I approach product development today.

    I do not begin by asking what features we can build.

    I begin by asking:

    What problem are we solving?
    Who experiences that problem?
    How painful is it?
    What would make someone change their current behaviour?
    Will they pay for the solution?

    THE HABIT

    I was always questioning the process

    I would often become bored with repetitive tasks, particularly when they seemed to exist only because nobody had questioned them.

    When I saw something being done manually again and again, I would immediately think about how it could be simplified, automated or removed.

    I also found it frustrating when management would not listen to an idea that could make something easier and quicker for customers.

    That frustration was never about challenging people for the sake of it.

    It came from struggling to understand why a business would continue with a slow or complicated process when there was a clearer solution available.

    I was constantly thinking about the entire journey.

    • What does the customer see?
    • What do they need to understand?
    • Where might they hesitate?
    • What information are we asking them to provide?
    • Which step creates unnecessary friction?
    • What could prevent them from completing the process?

    I eventually realised there was a name for this way of thinking.

    Product management.

    FROM MANAGING TO BUILDING

    I did not just want to manage products. I wanted to build them.

    My real education in product came from building my own ideas.

    Creating a product yourself forces you to think beyond screens, features and roadmaps.

    You have to understand the customer, the commercial model, the technology, the marketing, the operations and the route to revenue.

    You have to decide what matters now and what can wait.

    You have to test assumptions with limited time and limited money.

    You have to listen when the market tells you that something is not working.

    Most importantly, you have to prove that somebody values the solution enough to use it, recommend it or pay for it.

    Building my own products changed how I viewed product management.

    It was no longer about managing delivery.

    It became about creating meaningful outcomes.

    THE FILTER

    The questions behind everything I build

    Although my projects cover different industries, most of them begin with the same questions.

    Can this reduce the cost of living?

    Can it make travel, food, learning, entertainment or everyday services more affordable?

    Can this create new ways for people to earn?

    Can it help individuals use the skills, vehicles, spaces, knowledge or resources they already have?

    Can this create jobs in the future of AI?

    Can technology remove repetitive work while creating new opportunities built around creativity, judgement, relationships and human experience?

    Can it make an unnecessarily complicated experience simpler?

    Can we reduce the number of clicks, decisions, inputs or delays between a person and the outcome they need?

    These questions have influenced projects across shared commuting, affordable food, local working, music education, entertainment and AI powered services.

    The industries may change, but the purpose remains consistent.

    Build something useful.Make it easier to access.Create measurable value.Prove that people want it.

    POINT OF VIEW

    How I think about artificial intelligence

    Artificial intelligence will change the way almost every industry operates.

    Some tasks will disappear. Many roles will evolve. New types of work will emerge.

    I do not believe the answer is to resist that change.

    I believe the responsibility of product leaders is to make sure the benefits of that change are shared more widely.

    AI should remove unnecessary work, not human value.

    It should give people more time for creativity, communication, decision making and problem solving.

    It should make complex tools accessible to people who previously needed large budgets or specialist teams.

    It should help individuals build, create and compete.

    When I consider an AI opportunity, I do not only ask whether something can be automated.

    I ask who benefits from that automation and what new opportunities it can create.

    THE APPROACH

    From idea to measurable revenue

    My approach combines product thinking with commercial experience.

    I understand how to define a problem, shape a proposition, create an MVP and turn it into something that can be tested with real customers.

    But I also understand that a product is not successful simply because it has been launched.

    • It needs adoption.
    • It needs customer value.
    • It needs a commercial model.
    • It needs a credible path to revenue.

    That is the thinking behind the Crossley Method.

    A practical process for taking an idea from an early assumption to a working product with measurable commercial evidence.

    I am not interested in building features simply to make a roadmap look busy.

    I want to understand what will create the greatest result with the least unnecessary complexity.

    LENS

    What I see when I look at a product

    I do not see a screen.
    I see a journey.
    I do not see a button.
    I see a decision.
    I do not see a form.
    I see potential friction.
    I do not see a repetitive task.
    I see something that could be simplified, automated or removed.
    I do not see a feature request.
    I see a customer trying to solve a problem.

    And I do not see product management as the process of managing a backlog. I see it as the responsibility of turning real problems into useful, valuable and commercially sustainable solutions.

    THE REASON

    Why I became a Product Manager

    Looking back, I do not think I consciously decided to become a Product Manager.

    I spent years listening to customers, questioning processes, identifying friction and imagining better ways of doing things.

    Product management was simply the name of the role I had already been performing in my head.

    Today, my goal is bigger than building products that work.

    • Products that make everyday life more affordable.
    • Products that give people new ways to earn.
    • Products that help businesses grow.
    • Products that reduce unnecessary complexity.
    • Products that create opportunity in a world being reshaped by AI.

    That is why I became a Product Manager.

    Not because I wanted to manage features.

    Because I wanted to solve problems that matter.

    THE FRAMEWORK

    The Crossley Method: idea to first revenue in seven stages

    See the full method
    1. STAGE 1DiscoverWeek 1
    2. STAGE 2ValidateWeek 2
    3. STAGE 3PrototypeWeek 3
    4. STAGE 4Build MVPWeeks 3-4
    5. STAGE 5LaunchWeek 5
    6. STAGE 6First RevenueWeek 6
    7. STAGE 7ScaleOngoing

    Let us turn your idea into something customers value

    I work with founders and businesses that need more than another strategy document.

    Whether you are starting with an early idea, an underperforming product or a problem worth solving, I can help you define the opportunity, build the right version and create a path towards measurable revenue.

    From idea to working product. From working product to measurable revenue.

    © 2026 Andrew Crossley