woodysigner.
PT
← Back to projects

Case 01 / B2B product / Journey / Prototyping

Trade Flow
A digital letter-of-credit journey

A journey connecting client, supplier and bank, organizing drafts, documents, outstanding issues and next actions. The prototype explores how to track a letter of credit while preserving operational context.

Contribution

Product design and facilitation

Scope

Client · Supplier · Bank

Status

Demonstration prototype; production unverified

Evidence in the material

Context and challenge

A letter of credit connects commitments and documents between an importer, a supplier and a bank. The supplied HTML has separate client and bank analyst experiences; supplier review appears as a stage in the workflow.

Role and collaboration

According to the supplied professional history, my contribution includes product design, journey structuring and facilitation. Team composition and detailed responsibility allocation still need documentation.

Relevant constraints

The parties must agree before bank review. Documents, versions and outstanding issues need to remain connected to the request. The observed behavior is a demonstration, with no evidence of banking-system integration.

Guiding problem

How can a multi-actor operation become easier to understand and follow?

Design decisions

Proposed design decision

Make the next action explicit

The dashboard brings together recent requests, statuses and a recommended next action. The proposal aims to reduce the interpretation required before acting.

Proposed design decision

Separate agreement from submission

Submission is conditional on supplier approval and agreement confirmation. The prototype makes this dependency visible.

Proposed design decision

Keep history with the operation

The detail view combines a summary, timeline and next action to show what happened and what remains in the same context.

Proposed design decision

Distinguish client and analyst

The bank view organizes review and approval or rejection; the client view prioritizes creation and tracking.

Evidence in the material

Journey and flow

  1. Client creates a letter-of-credit draft
  2. Supplier reviews; client follows adjustments
  3. Client confirms agreement and submits to bank
  4. Analyst reviews documents and outstanding issues
  5. Bank records approval or rejection
  6. Client follows history and next steps

Screens and experience

Woodysigner / ArquivoProject imageDashboard, detail and request tracking
Internal screens need readable exports, reviewed and cleared for disclosure. This space does not represent a produced interface.
Evidence in the material

Documented iterations

Supplied version: v9_10

The HTML includes role selection, requests, creation and operation detail. Supplier review is represented through prototype states.

Interactions inspected in code

Confirmation before submission, version recording and rejection reasons are present. These interactions are simulated in the browser.

Contextual assistance limit

The chat uses predefined keyword-based responses. It is not evidence of an AI-model integration or production use.

Validation plan

Status and validation

Demonstration prototype; production unverified

No measured outcomes, interviews or user tests were supplied. Proposed tasks include locating an outstanding issue, identifying its owner and completing submission to the bank. Observe status comprehension, submission errors and need for support.

Hypothesis to validate

How can a multi-actor operation become easier to understand and follow?

Learnings

01 — A next action is useful when tied to a state and an actor’s responsibility.

02 — A timeline needs to explain dependencies as well as events.

03 — A navigable demo supports operational discussions; integration feasibility needs technical and domain review.

Case sources

  • v9_10_daycoval_trade_flow_demo_safe.html — reviewed structure and logic
  • Professional history supplied by Woody — design and facilitation contribution
Next caseTax Brain ↗