{
  "id": 20772295,
  "title": "Before You Build a Dashboard, Understand the Business Workflow",
  "url": "https://urgent.news/2026/11/19/before-you-build-a-dashboard-understand-the-business-workflow",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-19T16:43:57.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/hatemgheta/before-you-build-a-dashboard-understand-the-business-workflow-3lo9"
  },
  "original_language": "en",
  "account": "Developers often make the mistake of starting a software project with the user interface before understanding the underlying business workflow. A company may request a dashboard, and developers jump into designing cards, charts, and navigation menus. However, weeks later, the application remains unused as team members continue relying on spreadsheets, phone calls, and messaging apps to manage daily tasks. The issue isn't necessarily with the technology; rather, the problem lies in designing screens without first understanding the workflow.\n\nHaving experience in sales, digital marketing, and business development, the author emphasizes how software engineering should focus on business processes. They outline five principles for creating more useful business software:\n\n1. Start with decisions, not features. Instead of focusing on features like customer management or analytics, ask what decisions the system must support. For example, in a delivery operation, questions like \"Who should handle the next order?\" and \"What happens if a driver rejects an assignment?\" lead to business rules and ultimately technical requirements.\n\n2. Model the actual workflow. Consider a simplified delivery order flow: Created → Pending Assignment → Assigned → Out for Delivery → (Failed Attempt) → Reassigned → Delivered → Financial Settlement. This workflow reveals questions not addressed by a simple dashboard mockup, such as whether a completed order can revert to an active state, what happens when two drivers accept the same assignment, and how to handle API retries. These considerations impact the database design, permissions, APIs, background jobs, and audit records.\n\n3. Translate business rules into system invariants. A business rule should be enforced within the system. For instance, if an order can only have one active driver assignment at a time, this rule must be enforced at the data layer or within a synchronized transaction. A PostgreSQL partial unique index can enforce this constraint, preventing concurrent active assignments for the same order.\n\n4. Design for operational failures. Real businesses don't operate under perfect conditions. People make mistakes, connections fail, and external systems respond slowly. Imagine a delivery-completion request that times out. Without safeguards, retries could lead to duplicated financial operations or unwanted notifications. Implementing idempotency keys for operations that must not be repeated can help. For example, POST /api/orders/123/complete Idempotency-Key: completion-v1 ensures that retries return the previously recorded result.\n\n5. Build dashboards from trustworthy operations. Dashboards are valuable, but their usefulness depends on the quality of the data behind them. If a dashboard shows completed orders, it may not be helpful if there are multiple interpretations of what \"completed\" means. Does it mean the driver marked the order as delivered, the customer confirmed receipt, the merchant accepted the result, or the financial settlement was finalized? Similarly, sales and marketing metrics like leads, qualified leads, opportunities, and closed sales must have consistent definitions across teams. Before building analytics, define the business event being measured, the source of truth, the timestamp used, data ownership, and how corrections and reversals are handled. Reliable reporting starts with reliable operations.",
  "summary": "One of the most expensive mistakes in business software development is starting with the interface before understanding how the business actually operates. A company asks for a dashboard. The developer starts designing cards, charts, tables, and navigation menus. A few weeks later, the application looks impressive. But the team still relies on spreadsheets, phone calls, and WhatsApp messages to…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}