Put rules before clicks
Establish eligibility before asking the carrier to accept.
Connected Logistics / Full use case
Connected Logistics overview Throughput ceiling → eligibility → direct acceptance → operational movement.
Redwood Logistics / Self-Service Booking
Removing Human Work From Transactions That Didn’t Need It
Straightforward freight still required a broker or carrier representative to carry the transaction through the system.
IMPLEMENTED WORK · PORTFOLIO RECONSTRUCTION
Summary
Booking had plateaued near 250 loads a day. A roughly ten-step desktop workflow—with individual screens taking 10–15 seconds—consumed attention even when the transaction needed little judgment.
I helped redesign the path around direct acceptance for trusted carriers and eligible freight, while preserving broker involvement for negotiation, exceptions and uncertain cases.
Explore in Connected LogisticsCurrent prototype: Carrier portal → Available loads → View details. Offer review is available; the historical direct-acceptance task is shown in the reconstructed wireflow below.
Routine freight still passed through a person.
Mediated transaction
- Load available
- Representative finds and contacts carrier
- Carrier evaluates
- Representative records acceptance
- Internal system completes booking
Eligible self-service
- Load + carrier qualify
- Carrier receives the opportunity
- Carrier reviews and accepts
- Booking is recorded
Simplified workflow reconstruction. The pilot used emailed offers to selected trusted carriers for suitable straightforward loads.
If a person is only carrying known information between steps, that handoff is a candidate for self-service.
The tension
Routine transactions competed with exceptions for attention.
The same mediated path served straightforward loads and freight that genuinely needed an expert.
Where judgment mattered
Unusual equipment, difficult lanes, negotiation, customer restrictions, uncertain capacity, accessorials, relationships and exceptions.
Keep a person in the decision.
Where coordination added friction
Known terms and a suitable, trusted carrier—but an internal representative still had to relay and record acceptance.
Carriers waited. Redwood spent human attention moving information.
Which parts of booking should no longer require an internal person at all?
Research → legacy mediated workflow
- 01Carrier interestThe carrier wants the load.
- 02Representative finds / reviews loadAn internal person opens the opportunity.
- 03Internal multi-step workflowNavigation and waiting persist even for routine freight.
- 04Representative records acceptanceKnown information is relayed into the system.
- 05Booking completesThe intermediary carries the transaction through.
Research + system
The workflow itself had become part of the constraint.
Adding representatives did not remove navigation, waiting and repeated handling from a roughly ten-step desktop path.
~250 / dayPrior practical booking ceiling
~10 stepsLegacy internal booking path
10–15 secondsIndividual legacy screen loads
OBSERVED BEHAVIOR
Representatives used the external acceptance flow themselves.
Representatives began using the carrier-side link on drivers’ behalf because it was easier than the internal workflow. That behavior exposed the friction without requiring anyone to argue that the new path was simpler.
Users routed around the old workflow.
Why a smaller pilot came before the larger marketplace
An executive carrier-marketplace prompt became a working prototype in four business days for an investor presentation. The team then chose a narrower behavior test: emailed offers for selected simple or dedicated loads, accepted directly by trusted carriers.
The larger concept made the service model discussable. The smaller pilot tested whether routine booking could move without a broker call, before investing in the whole marketplace.
How the problem changed
- 01Routine freight enters the queueThe transaction may need little judgment.
- 02Broker / rep carries itRoutine and difficult freight compete for attention.
- 03Repeated checks are predictableSeparate administration from expertise.
- 04Eligibility moves upstreamEstablish confidence before offering direct action.
- 05Trusted carrier accepts directlyRemove the handoff for eligible freight.
The pattern
Automate certainty. Preserve judgment.
A shorter interaction depends on confidence in both the participant and the transaction.
Early design / decision model
- 01Load availableKnown requirements and terms.
- 02Evaluate self-service eligibilityIs there enough confidence in the carrier and transaction?
DecisionEligible for self-service?
Yes → direct offerTrusted carrier reviews and accepts
The operational system records the acceptance.
No → broker workflowPreserve negotiation and expert judgment
Uncertain capacity, requirements or terms stay with a person.
IMPLEMENTED PILOT
Trusted carrier + suitable load
Selected straightforward or dedicated freight went through an emailed opportunity with direct review and acceptance. The reported +15% throughput result belongs to this narrow pilot.
Decision: accept known terms without requiring an internal person to relay the answer.
HUMAN JUDGMENT
Uncertain, negotiated or exceptional
Complex requirements, pricing negotiation, capacity uncertainty and relationship-sensitive freight still need broker involvement.
Decision: investigate or negotiate instead of forcing the load through direct acceptance.
CONCEPT
A broader service model—not a launched marketplace
The rapid prototype explored a larger carrier experience. It led to a cheaper behavior test, not a claim that every marketplace capability was implemented.
Decision: test the core self-service behavior before building the broader product.
RECONSTRUCTION
The rules did work before the button appeared.
Participant
Trusted carrier, relevant availability and compatible equipment.
Transaction
Known route, requirements and terms; no unresolved condition requiring negotiation.
Interaction
Review essential details → Accept Load
Generalized eligibility model, not an audited production rules matrix. Route, equipment/accessorials, preferences, availability, customer restrictions, insurance/certifications, pricing and margin can affect eligibility; this generalized model does not disclose or verify exact historical production rules.
The UI became simpler because more of the decision was resolved before it appeared.
Design decisions
Make the happy path shorter. Keep the exception path available.
Self-service must commit to the operational workflow—not create another message for someone to re-enter.
Focus on the decision
Prioritize route, timing, equipment, rate and relevant requirements—not the whole internal application.
Keep a path to help
Return ambiguous or exceptional transactions to a broker.
Trust selectively
Confidence in the participant does not make every load suitable for self-service.
Make completion authoritative
Acceptance needs to update booking, not leave someone backstage retyping the answer.
Detailed acceptance workflow
- 01 · Entry point
Receive the offer
Schematic view / evidenceEligible freight offered to a selected trusted carrier.
- User action
- Open the offer.
- System / shared response
- The essential opportunity becomes available for review.
- 02 · Workflow state
Review load details
Schematic view / evidenceOrigin / destination · timing · equipment · rate · relevant requirements.
- User action
- Review the terms that determine whether this load can be serviced.
- System / shared response
- The focused view exposes the decision without the full internal booking application.
- 03 · Workflow state
Confirm eligibility
Schematic view / evidenceThe known carrier and load requirements still fit.
- User action
- Proceed only while the offered terms and requirements remain valid.
- System / shared response
- A changed requirement or exception exits direct acceptance.
DecisionCan this offer still be accepted directly?
Eligible → acceptCarrier deliberately accepts
The booking is recorded and authoritative confirmation replaces relay or duplicate entry.
Changed requirement / exception → assistanceReturn to broker coordination
Resolve the changed terms or missing context. Do not imply a completed booking.
Resulting state / return to evidenceBooking confirmed, or broker assistance required
These are distinct resulting states. Direct acceptance commits the transaction; the exception path keeps human judgment available.
Pilot email versus marketplace
Implemented pilot
Email → Book Now
Selected trusted carriers could review and accept suitable freight directly. The first test had one response path.
Broader designed response set
Five ways to respond
- Book Now
- Make an Offer → success / failed counteroffer
- No Capacity
- Manage Lane
- Unsubscribe
Evidence → Decision → Tradeoff
- 01EvidenceRoutine mediation consumes human attention.
- 02DecisionDirect acceptance for eligible freight.
- 03TradeoffEligibility must remain trustworthy.
- 04ResponseKeep a human path for exceptions.
Review the freight requirements before acting
Impact in reality
A reported +15% gain in the one-click pilot.
Keep the outcome, prior constraint and later performance observation separate.
Practical booking ceiling
The earlier operating plateau—not a post-pilot total or a per-representative target.
Typical screen interactions
Legacy individual screens commonly took 10–15 seconds. The newer web experience was closer to two seconds during partial rollout—not every transaction or screen.
Portfolio interpretation · more than fewer clicks
The outcome suggests the opportunity was not merely interface efficiency. Removing waiting for an intermediary, repeated communication, context switching and re-entry of known information could create more capacity than a screen-only improvement.
This is interpretation, not a measured causal breakdown. The pilot and later latency observations do not establish how much each source of friction contributed.
Direct acceptance
Simplified external acceptance for selected trusted carriers and eligible freight, connected to operational booking.
Broader web modernization was separate work.
Users chose the shortcut
Representatives used the external link themselves. Pilot success helped support continued investment in Load Board and booking modernization.
A connected lifecycle
Customer shipment state, broker load management, carrier opportunities, bids/awards and direct acceptance are brought together in the current prototype.
The unified prototype is not the historical product architecture.
Outcome evidence
Expected improvement3–5%
Initial projection for the narrow acceptance pilot.
Observed throughput+15%
Bid-processing throughput from one-click acceptance.
BoundaryOne pilot
Not a carrier-matching KPI or a result for the full marketplace.
Reality check · what still needed people
What self-service improved
Routine coordination, carrier friction and booking throughput for straightforward freight.
Where expertise remained
Negotiation, relationships, unusual equipment, difficult lanes, customer rules, pricing exceptions, uncertain capacity and service failures.
The goal was not fewer people. It was fewer situations where people were forced to behave like middleware.
From mediated transaction to trusted self-service
- Map why the handoff exists.
- Separate judgment from administration.
- Identify deterministic eligibility.
- Move rules upstream.
- Focus the interaction on the decision.
- Commit directly to the system.
- Preserve expert intervention.
- Measure operational movement.
Useful anywhere a trusted participant can safely complete a routine transaction without an intermediary.
Connected Logistics: understand the state → automate the certain → support the uncertain.