<aside> 💡

129Knot is the e-procurement system of a private Singapore-based oil and gas corporation, designed to digitize the entire process from supplier registration and bidding to payment, enhancing efficiency and transparency in procurement operations.

</aside>

About Project

Product Overview

• This is the B2B e-commerce platform implemented by 129knots. It enables registered suppliers to sell non-stock and non-contract items directly to internal business units.
• The platform functions as a closed ecosystem between buyers and registered suppliers, ensuring a secure and efficient procurement environment

The Role

I collaborated with the PM, account team, and client to deliver the MVP of 129knots. I designed the flow for creating bid profiles and participating in online bidding, optimized for mobile devices, and worked closely with engineers to ensure a seamless implementation. After launch, we iterated based on feedback and expanded the product to support full B2B integration.

The Problem - Objectives & Goals

1. Tendering in oil & gas is lengthy, with multiple steps and specialized technical requirements.

   <aside> 💡

   • Conduct traditional user surveys to build accurate new user journeys.
   • Develop a service blueprint to define user interactions and system layers.
   • Break down the process into smaller functional modules that are easier to design, test, and iterate. </aside>

2. Buyers and suppliers have different goals and behaviors, requiring tailored UX and role-based interfaces.

   <aside> 💡

   • Use role-based dashboards to separate buyer and supplier interfaces.
   • Design unique onboarding experiences for each user type.
   • Build detailed personas for both groups to ensure flows are tailored. </aside>

3. Private clients may lack clear internal workflows, forcing designers to define UX flows from scratch.

   <aside> 💡

   • Combine UX research and stakeholder interviews to reconstruct the real-life workflow.
   • Suggest best practices based on global platforms (e.g., SAP Ariba, Coupa, Jaggaer).
   • Build early prototypes and test them with real users to validate the flow. </aside>

4. Public auctions must prevent tampering and ensure tender data confidentiality.

   <aside> 💡

   • Implement data encryption, digital signatures, and multi-factor authentication.
   • Add immutable audit logs for every bid or interaction in the auction process.
   • Use real-time bidding interfaces that clearly show prices, time left, and participants (if public). </aside>

Ideate & Deliver

My team and I came up with many scenarios, but after multiple discussions and alignment with the client, we decided to visualize everything in the most clear and understandable way.

The first version & The release version

<aside> 💡

As is :

</aside>

<aside> 👉

Will be:

</aside>