5 min read

Building product foundations for a large agricultural digital ecosystem

Building product foundations for a large agricultural digital ecosystem

Client

Large agricultural cooperative

My role

Lead Product Designer

Timeline

2024 - Present

Overview

The problem

When I joined, the company was building its digital practice across many business lines, products and user groups. Teams were working with legacy systems, fragmented services and business rules shaped by agriculture, commerce, logistics and field operations. The challenge was to create modern digital products without ignoring how the business actually works on the ground.

The solution

I created a reusable product design base and applied it across several digital products, from business apps and member services to B2B commerce and field-team workflows. I worked between business teams, IT, developers, external partners and users to turn dense operational rules into usable journeys, shared patterns and delivery-ready designs.

Who I worked with

Business apps, commerce and farmer services

Setting product direction

Business stakeholders

Product owners

IT leadership

Commerce teams

Marketing teams

Domain experts

Turning work into delivery

Developers

External partners

Backend teams

Data & BI teams

Field teams

Farmers and end users

What I worked on

Commerce, field teams and farmer services

Product design base

Business apps

B2B commerce

Member services

Field sales flows

User research

What I worked on

Commerce, field teams and farmer services

Product design base

Business apps

B2B commerce

Member services

Field sales flows

User research

What I worked on

Commerce, field teams and farmer services

Product design base

Business apps

B2B commerce

Member services

Field sales flows

User research

Approach

Building a product design practice across a digital ecosystem

Four moves to turn scattered business needs into reusable product work across business apps, commerce, field teams and farmer-facing services.

Set the design base

Created the design system, UI rules and reusable patterns needed to support several product types.

Turn business rules into flows

Mapped pricing, stock, delivery, accounts and user roles into journeys people could actually use.

Align teams around delivery

Worked with business, IT, developers and external partners to move from requests to validated designs.

Bring field feedback into the loop

Used field visits, user tests and team feedback to adjust decisions before delivery.

Building a product design practice across a digital ecosystem

Four moves to turn scattered business needs into reusable product work across business apps, commerce, field teams and farmer-facing services.

Set the design base

Created the design system, UI rules and reusable patterns needed to support several product types.

Turn business rules into flows

Mapped pricing, stock, delivery, accounts and user roles into journeys people could actually use.

Align teams around delivery

Worked with business, IT, developers and external partners to move from requests to validated designs.

Bring field feedback into the loop

Used field visits, user tests and team feedback to adjust decisions before delivery.

Building a product design practice across a digital ecosystem

Four moves to turn scattered business needs into reusable product work across business apps, commerce, field teams and farmer-facing services.

Set the design base

Created the design system, UI rules and reusable patterns needed to support several product types.

Turn business rules into flows

Mapped pricing, stock, delivery, accounts and user roles into journeys people could actually use.

Align teams around delivery

Worked with business, IT, developers and external partners to move from requests to validated designs.

Bring field feedback into the loop

Used field visits, user tests and team feedback to adjust decisions before delivery.

01. Set the design base

Before larger product work could move at speed, the company needed a shared visual and interaction base. I translated the existing brand into a practical product language: rules, components, responsive behaviours and reusable patterns. This gave teams a common starting point for web apps, mobile journeys, B2B commerce and field-team products.

Product design base

Focus areas

  • Brand translation

  • Tokens and variables

  • Reusable components

  • Responsive patterns

  • Accessibility basics

  • UI documentation

Product design base

Focus areas

  • Brand translation

  • Tokens and variables

  • Reusable components

  • Responsive patterns

  • Accessibility basics

  • UI documentation

Reusable product patterns

Shared UI language

  • Navigation patterns

  • Form behaviours

  • Status messages

Reusable product patterns

Shared UI language

  • Navigation patterns

  • Form behaviours

  • Status messages

Delivery-ready foundations

Built for reuse

  • Web and mobile journeys

  • Commerce and service flows

  • Future product work

Delivery-ready foundations

Built for reuse

  • Web and mobile journeys

  • Commerce and service flows

  • Future product work

02. Turn business rules into flows

The hardest part was not making the interface look modern. It was turning dense agricultural, commercial and operational rules into flows people could use without seeing the machinery behind them. I worked with business and technical teams to map pricing, stock, delivery, accounts, user roles and seasonal cases, then translated them into product journeys.

Commerce journeys

From browse to order

  • Product listing

  • Product detail

  • Cart and checkout

Commerce journeys

From browse to order

  • Product listing

  • Product detail

  • Cart and checkout

Field sales workfows

Built for reuse

  • Quick product selection

  • Customer context

  • Order assistance

Field sales workfows

Built for reuse

  • Quick product selection

  • Customer context

  • Order assistance

Business rules mapping

Focus areas

  • User roles

  • Account switching

  • Pricing logic

  • Stock availability

  • Delivery states

  • Seasonal cases

  • Restricted products

Business rules mapping

Focus areas

  • User roles

  • Account switching

  • Pricing logic

  • Stock availability

  • Delivery states

  • Seasonal cases

  • Restricted products

03. Align teams around delivery

Design quality depended on what happened between the first business request and the final release. I worked as the bridge between business teams, IT, developers, external partners and users, turning scattered requests into shared decisions and delivery-ready designs. The goal was to reduce blind spots before development and help teams move faster with fewer late surprises.

Cross-functional product workflow

04. Bring field feedback into the loop

The product could not be designed from meeting rooms only. I brought user feedback into the process through field visits, interviews, remote tests and workshops with farmers and field teams. These sessions helped expose misunderstandings early, especially around pricing, availability, loyalty points, account access and delivery logic.

User testing

Tested topics

  • Pricing visibility

  • Discount logic

  • Cart feedback

  • Address impact

  • Loyalty points

  • Reward usage

  • Account access

User testing

Tested topics

  • Pricing visibility

  • Discount logic

  • Cart feedback

  • Address impact

  • Loyalty points

  • Reward usage

  • Account access

Field research

What I looked for

  • Daily habits

  • Pain points

  • Decision moments

Field research

What I looked for

  • Daily habits

  • Pain points

  • Decision moments

Product decisions

What changed

  • Clearer labels

  • Safer edge cases

  • Simpler journeys

Product decisions

What changed

  • Clearer labels

  • Safer edge cases

  • Simpler journeys

Impact

Dimension

The outcome

Scalability

A reusable product design base made it easier to work across several digital products, from business apps and member services to B2B commerce and field-team flows.

Velocity

Reusable components, shared rules and delivery-ready designs helped teams move faster without restarting from zero on every new product.

Quality

User testing and field feedback exposed misunderstandings early, especially around pricing, availability, loyalty points and delivery logic.

Alignment

Business, IT, developers, external partners and field teams had a stronger common ground for turning business needs into usable product decisions.

Adoption

Product decisions were shaped around real farming habits, field sales routines and operational needs, making the digital experience easier to understand and trust.

Screens are the output. The real work is changing how products get made.

Dimension

The outcome

Scalability

A reusable product design base made it easier to work across several digital products, from business apps and member services to B2B commerce and field-team flows.

Velocity

Reusable components, shared rules and delivery-ready designs helped teams move faster without restarting from zero on every new product.

Quality

User testing and field feedback exposed misunderstandings early, especially around pricing, availability, loyalty points and delivery logic.

Alignment

Business, IT, developers, external partners and field teams had a stronger common ground for turning business needs into usable product decisions.

Adoption

Product decisions were shaped around real farming habits, field sales routines and operational needs, making the digital experience easier to understand and trust.

Screens are the output. The real work is changing how products get made.

©2026 Guillaume Dusseux-Gicquel

guillaume.dusseuxgicquel@gmail.com

©2026 Guillaume Dusseux-Gicquel

guillaume.dusseuxgicquel@gmail.com

©2026 Guillaume Dusseux-Gicquel

guillaume.dusseuxgicquel@gmail.com