Module 5: Best Practices in Structuring a Solution

Introduction to Structuring Solutions on Rise-X 🌅

Structuring a solution on Rise-X is the process of translating real-world business problems into an efficiently designed ecosystem, ensuring efficiency, scalability, transparency, and collaboration. This module assumes that you already have a specific use case in mind. If you dont already have a business problem in mind read modules 2 and 3 to find out how Rise-X can help your business.

The more you learn about how to use configure ecosystems on the Rise-X platform the easier it is to design a solution from a real-world use case. You may find it useful to revisit this module after going through the rest of the academy.

How to Map Real-World Processes onto Rise-X 🌏

1. Identify and outline the Use Case

• Identify a business challenge that Rise-X is particularly good at solving, usually this will be something relating to multi-party business processes.
• Identify stakeholders (e.g., internal teams, suppliers, regulators).
• Outline the steps that happen in the business process identifying who captures what data at that time both in your business and in other parties involves in the process.

2. Design the Workflows

• Workflows should be used to capture a single process that has a relatively predetermined timeframe.
• If the process takes more than a month, a rule of thumb is that it should be split into multiple workflows.
• Tasks within workflows should be defined as one party filling in data at one point in time.
• Try to have the minimum number of tasks while not breaking the rules of:
• Each task should be completed at one time (e.g. not across a whole month).
• Each task should be completed by only one party (e.g. not getting a supplier and buyer contributing to the same task).
• Identify what data needs to be captured at each task.

3. Define Assets

• Use assets when data needs to persist across multiple workflows (e.g. a "Product" asset used in procurement and inventory workflows).

4. Establish Workflow and Asset Links

• Workflows ↔ Workflows: Automate multi-step processes (e.g. "Supplier Approval" triggers "Order Fulfilment").
• Workflows ↔ Assets: Ensure workflows update or reference assets as needed.
• Assets ↔ Assets: Maintain structured relationships between assets (e.g. "Shipment" asset links to "Product" asset).

5. Sense Check

• Does the solution that has been designed solve the pain point / business problem that you initially had?
• If yes, that great! let’s get building in the next few modules!
• If no, it may be worth revisiting your use case to see if it’s something that Rise-X can solve or your designing of a solution on Rise-X and seeing if there can be changes here to solve your problem.

Best Practices for Structuring Solutions 👷

A. Start Simple

• Focus on one core problem and build a solution around it.
• Example: Automate a single approval process before scaling to more complex workflows.

B. Iterate and Improve

• Start with a basic workflow, create it on Rise-X, roll it out, gather feedback, and refine it over time.
• Example: Add more steps or integrate additional assets as your process evolves.

C. Leverage Workflow Geniuses

• If structuring a solution feels overwhelming, Rise-X’s Workflow Geniuses can help architect the perfect solution.
• You can contact the Rise-X team to find out more about Workflow Geniuses either by email or by booking a meeting.

Real-World Example: Cargo Shipment Tracking 🚢

Problem:

Shipping companies, freight forwarders, and buyers struggle with fragmented shipment data, leading to delays, miscommunication, and disputes over delivery status, cargo conditions, and compliance. Each party maintains separate records, making real-time coordination difficult.

Solution:

1. Workflow: "Cargo Shipment Lifecycle"
• Steps: "Shipment Created" → “Customs Documents Submitted" → "Cargo Loaded" → "Cargo Check and Departure" → "Arrived at Port" → "Customs Clearance" → "Delivered & Verified."
2. Assets:
• "Bill of Lading" asset acts as a shared proof of shipment, accessible to all stakeholders.
• "Condition Report" asset logs temperature, damage reports, and handling conditions.
3. Stakeholders:
• Shipping Company updates real-time tracking and cargo handling status.
• Freight Forwarder ensures customs clearance and regulatory compliance.
• Buyer/Receiver verifies shipment details and delivery conditions.

Outcome:

• A single source of truth ensures all parties have access to the same real-time shipment data, reducing disputes.
• Faster issue resolution when delays or damage occur, as records are instantly accessible.
• Improved compliance and auditability, with a shared, tamper-proof history of the shipment lifecycle.

Key Takeaways 🔑

• Identifying the right use case and designing it correctly is important to get the most value out of Rise-X.
• You can follow the guidelines in this guide to design a Rise-X solution or you can get the help from a Workflow Genius.
• Start small then work up from there!

Continue Learning 🚶‍♀️‍➡️

• The next module in the Rise-X Academy covers how to create workflows on Rise-X, check it out here.