From bc912ecbf4aa1c3b0094aae1206538c4c3c5b8d1 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Wed, 7 Jan 2026 18:28:04 +0200 Subject: [PATCH 01/31] Add Cases subpage for Project Management Introduces a dedicated Cases subpage under Project Management, explaining how tasks are executed, tracked, and managed in ERP.net, including context, communication, hierarchy, backlog, and Kanban flow. --- features/work-management/cases.md | 196 ++++++++++++++++++++++++++++++ 1 file changed, 196 insertions(+) create mode 100644 features/work-management/cases.md diff --git a/features/work-management/cases.md b/features/work-management/cases.md new file mode 100644 index 00000000..2dc0dbca --- /dev/null +++ b/features/work-management/cases.md @@ -0,0 +1,196 @@ +# Cases +## Where tasks turn into real work + +At the core of every project activity are concrete tasks. +They define what needs to be done, by whom, within what timeframe, and in what context. + +The clearer these tasks are defined and managed, the more predictable the work becomes — both for teams and for management. +That is why task management is not an operational detail, but a key element of project management as a whole. + +Many organizations sense this intuitively — work gets done, but context, decisions, and progress are often managed across multiple tools. + +--- + +## The core instrument: Cases in Project Management in @@name + +In Project Management in @@name, work execution is organized through **Cases**. +They are the place where tasks are planned, taken on, executed, and tracked — without losing context along the way. + +Each Case brings together everything needed for real work: +who is responsible, what the priority is, what the current status is, what has been discussed, which documents are involved, and how the process has evolved over time. + +This transforms a Case from a simple task into a complete unit of work — one that can be managed, analyzed, and extended. + +The way Cases are designed allows teams to start with minimal information when needs are simple, and gradually add structure, detail, and control as projects grow more complex and requirements increase. +As a result, Cases remain comfortable for everyday operational work while being fully suitable for large-scale projects with extensive coordination and business-level accountability. + +--- + +## What a Case represents in @@name + +A Case in @@name is not just a task to be checked off. +It is a focal point of work — the place where an intention becomes real execution. + +A Case can start and finish very simply — with just a name and an owner. +Exactly as much as is needed to move work forward. + +As work evolves, the Case can naturally grow with it. +Priority, deadlines, statuses, descriptions, notes, and links to other tasks can be added — only when the business process requires it. + +A Case brings together in one place: + +- responsibility and deadlines +- current state and full history +- internal discussions and comments directly related to the work +- files and documents used in the process + +This way, a task is never “bare” — it always carries its context. + +--- + +## A workspace, not just a record + +A Case in @@name is designed as a workspace, not a static object. + +Within a Case, users can: + +- track time directly while working +- define estimated time when planning is required +- use Story Points when the team works that way +- associate the Case with a Sprint when work is iterative + +A Case can also be linked: + +- to a specific project +- to a Social Group when the task concerns a particular team +- to a Party (customer, partner, or counterparty), independently of who the task is assigned to + +This allows tasks to be viewed not only as “who does what”, but also **for whom** and **in what business context**. + +--- + +## Control over time and state — when it is needed + +Cases support different time-related states, such as readiness, waiting, or completion moments. +These markers make it possible to analyze how work actually flows, without adding burden to daily operations. + +By default, tasks move through standard states such as **Backlog**, **In Progress**, **Waiting**, or **Closed**. +When a business follows a more specific process, these states can be extended and adapted through custom **User States**. + +The system does not impose a model — it follows it. + +--- + +## Simplicity on the surface, depth underneath + +The most important aspect of Cases is that no one is required to use everything at once. +Teams can work in a light and intuitive way, while the system remains ready to support more structure, control, and accountability whenever needed. + +This combination — ease of use with real depth — makes Cases suitable both for everyday tasks and for complex project environments. + +--- + +## Context and communication — part of the task itself + +One of the greatest strengths of Cases is that all communication can take place directly within the task. + +Discussions, decisions, and clarifications do not get lost in emails or chats — they remain part of the Case history. +This provides clear answers to questions such as: + +- why a certain decision was made +- what was discussed +- who was involved + +Context stays with the work — even as people or priorities change. + +--- + +## Hierarchy and focus in execution + +Cases allow tasks to be managed hierarchically. + +A Case can contain subcases, making it possible to: + +- break down larger activities into logical steps +- clearly distribute responsibilities +- preserve the connection between overall goals and concrete actions + +This is especially valuable in more complex projects and cross-team coordination. + +--- + +## When work has a clear entry point and a clear flow — Backlog and Kanban + +In real work, tasks do not arrive neatly ordered. +Ideas, requests, improvement proposals, issues, and commitments constantly emerge — from customers, teams, and management. + +That is why in Project Management in @@name, **Cases begin their life in the Backlog** — the place where all upcoming work is collected, organized, and prioritized. +The Backlog answers the question *“What’s next?”* without creating pressure or a sense of overload. + +How this work is planned and organized is entirely in the hands of the teams. +Users decide which Cases from the Backlog are ready to be taken on, when, and with what priority — turning planning into an active process rather than a static list. + +From there, **Kanban visualization turns planning into action**. +With an intuitive drag-and-drop interface, Cases move between statuses — from idea, through preparation and execution, to completion — directly from the visual view. + +This allows teams to see at a glance: + +- what is currently in progress +- which Cases are waiting for input or decisions +- which Cases are planned +- which Cases are completed + +Kanban in @@name is more than visualization. +It is a tool for focus, balance, and consistency — a way for work to move forward without losing control over priorities. + +The Backlog secures the **input** of work. +Kanban manages its **flow**. +And Cases are where all of this happens — in a clear business context. + +--- + +## Business benefits: what the business gains from Cases + +When tasks are managed through Cases in @@name, the business gains far more than an organized task list. + +### Clear responsibility and traceability +Every task has an owner, a history, and context — decisions and actions remain visible over time. + +### Better coordination between teams +People work in a shared space where communication, files, and progress are transparent to all involved. + +### Less operational friction +Documents, discussions, and time tracking happen where work is done — without unnecessary switching between tools. + +### Predictable and controllable execution +Progress is visible, delays are detected early, and management decisions are based on real information. + +--- + +## Applicability: where Cases work best + +Cases are especially valuable where work is not one-off, but evolves over time and involves people, decisions, and context. + +### Client and project work +When multiple tasks are performed for a client or project, each Case can represent a specific activity — with owner, deadline, discussion, and documents. +This keeps the full history of work traceable: what was requested, agreed upon, and delivered. + +### Internal initiatives and improvements +Cases bring the same clarity to internal work as to client projects. +Ideas and improvements do not get lost — they become concrete tasks with visible progress. + +### Operational coordination across teams +When multiple roles or departments are involved, the Case becomes a shared point of work. +Everyone sees the current state, participates in discussion, and works with the same information. + +### Services and time-accountable activities +Cases are a natural choice when it is important to know how much time was spent, on which task, and for what outcome. +Time tracking directly from the Case makes the connection between effort and results fully transparent. + +--- + +## What’s next + +👉 **Back to the main topic:** [Project Management in @@name](project-management.md) +👉 **Read more about:** [Areas, Project Groups, and Milestones — managing project structure and scale](areas-project-groups-milestones.md) + From 1fd9659e54e2aac64357d9b79ec8d30f6e81c05f Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Thu, 8 Jan 2026 17:58:57 +0200 Subject: [PATCH 02/31] Image Update in project-management.md Image Update in project-management.md --- features/work-management/project-management.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/features/work-management/project-management.md b/features/work-management/project-management.md index 79f0f20c..5a66ad46 100644 --- a/features/work-management/project-management.md +++ b/features/work-management/project-management.md @@ -24,6 +24,10 @@ It would be wonderful if there were a place that gathers all of this — officia Fortunately, there is. +project-management-home + +*The Project Management workspace in @@name brings projects, tasks, time, structure, and process into one unified view.* + --- ## There Is an Easier Way to Manage Your Projects From f5e685448b0baa66c10962c140034f304c54b1f4 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 11:00:03 +0200 Subject: [PATCH 03/31] Add Areas, Project Groups, and Milestones subpage for Project Management Adds a new Project Management subpage explaining how Areas, Project Groups, and Milestones help structure projects as they grow in scope and complexity. The article focuses on: - Organizing projects into logical areas and phases - Managing programs of related projects through Project Groups - Using milestones to create orientation and rhythm without adding overhead Includes navigation links to the main Project Management page and related subpages. --- .../areas-project-groups-milestones.md | 146 ++++++++++++++++++ 1 file changed, 146 insertions(+) create mode 100644 features/work-management/areas-project-groups-milestones.md diff --git a/features/work-management/areas-project-groups-milestones.md b/features/work-management/areas-project-groups-milestones.md new file mode 100644 index 00000000..6118056c --- /dev/null +++ b/features/work-management/areas-project-groups-milestones.md @@ -0,0 +1,146 @@ +# Areas, Project Groups, and Milestones + +## When projects start to “think bigger” + +At the beginning, tasks are enough. + +The team knows what needs to be done, who takes responsibility, and how the work is progressing. + +Over time, however, projects begin to grow. + +More initiatives appear. More people are involved. More parallel activities take place. + +The work is no longer just a list of tasks, but a system of connected efforts that must be coordinated, structured, and managed on multiple levels. + +Naturally, the focus begins to shift: + +- from individual tasks to the overall structure +- from what we are doing today to where we are in the bigger picture +- from execution to managing scale and progress + +This is the moment when Project Management stops being a purely operational tool and becomes a management system. + +In @@name, this transition happens through **Project Groups**, **Project Areas**, and **Milestones** — tools that give projects shape, logic, and rhythm, without complicating the teams’ everyday work. + + +## The structure that makes scale manageable + +When projects begin to operate on more than one level, structure is no longer a formality — it becomes a necessity. + +It helps teams navigate their daily work, and it allows management to see the full picture and make more informed decisions. + +In the Project Management module of @@name, this structure is built through three complementary elements that extend the work with Cases and add clarity, scale, and rhythm. + + +## Project Groups – managing programs of projects + +Project Groups allow projects to be combined into logical groupings based on how the business manages them. + +These may be strategic initiatives, client programs, internal transformations, product lines, or any other categorization that makes sense for the organization. + +At this level, the focus moves away from individual tasks and toward: + +- the relationships between projects +- the overall progress of the program +- priorities and workload at a higher management level + +Project Groups form the foundation for **Program Management** — a capability that gives management direction and control, without burdening teams with additional complexity. + +### Managing budget at program level + +Project Groups in @@name also allow projects to be managed financially at a higher level. + +Management can track: + +- planned and actual budgets for the entire program +- costs across multiple related projects +- budget distribution and reallocation when priorities change + +This makes Project Groups especially valuable for organizations managing strategic initiatives, client programs, or long-term investments. + + +## Project Areas – logic inside the project + +While Project Groups operate above projects, Project Areas introduce structure within them. + +They allow tasks inside a project to be organized by meaning, phase, or functional logic. + +Project Areas are particularly useful when: + +- a project passes through clearly defined stages +- there are parallel streams of work +- different teams or roles contribute to the same objectives +- task complexity increases over time + +### Phases, streams, and reusable structures + +Project Areas can represent phases such as Planning, Execution, Testing, or Go-Live. + +They can also reflect functional domains, responsibility areas, or types of work. + +A key advantage is that the same Project Area can be reused across multiple projects, creating consistency and enabling cross-project analysis. + +This allows management to see how specific phases or workstreams evolve across different initiatives, while teams benefit from clearer structure and focus. + + +## Milestones – when progress has clear reference points + +Milestones introduce clear reference points in the life of a project. + +They mark important stages, outcomes, or decisions and help answer a simple but critical question: + +**Where are we right now?** + +Milestones: + +- create a sense of progress +- improve communication with stakeholders +- support planning and accountability + +In @@name, Milestones are designed to support orientation and results without introducing unnecessary administrative overhead. + +They provide a shared language between teams and management — progress can be discussed clearly without diving into operational details. + + +## Business benefits – what the business truly gains + +The combination of Project Groups, Project Areas, and Milestones transforms project management into a sustainable management approach. + +For the business, this means: + +- **Easier management as scale increases** + Projects grow without chaos or constant firefighting. + +- **Clear logic instead of scattered information** + Work is structured by meaning, phase, and responsibility. + +- **Visibility at the right level for everyone** + Teams, project managers, and executives each see what matters to them. + +- **Less operational noise, more autonomy** + Fewer clarification meetings, fewer status questions, more focus on execution. + + +## Applicability in real-world work + +These tools are particularly valuable for organizations that: + +- manage multiple parallel projects +- run client implementations with defined phases +- coordinate internal programs and transformations +- seek balance between flexibility and management control + +Whether it is a short initiative or a long-term program, the approach remains the same: +**clear structure, shared context, and visible progress.** + + +## Continue exploring Project Management + +**Back to the previous topic:** +[Cases – tasks as real work](https://info.erp.net/features/work-management/project-management/cases.html) + +**Read next:** +[Types, Case Categories, and WIP limits — managing workflow and flow control](https://info.erp.net/features/work-management/project-management/types-case-categories-wip-limits.html) + +**Back to the main topic:** +[Project Management in @@name](https://info.erp.net/features/work-management/project-management.html) From c5686da285403921816f8fec578edec86077f366 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 11:18:25 +0200 Subject: [PATCH 04/31] Update areas-project-groups-milestones.md Introduction revised --- .../areas-project-groups-milestones.md | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/features/work-management/areas-project-groups-milestones.md b/features/work-management/areas-project-groups-milestones.md index 6118056c..c97dce27 100644 --- a/features/work-management/areas-project-groups-milestones.md +++ b/features/work-management/areas-project-groups-milestones.md @@ -2,6 +2,11 @@ ## When projects start to “think bigger” +In this article, we continue exploring the building blocks of Project Management in @@name — focusing on the tools that help teams and managers understand where work fits, how projects relate to each other, and how progress is measured over time. + +Project Groups, Project Areas, and Milestones are the elements that make this possible. +They give projects shape, logic, and rhythm — without adding unnecessary complexity to everyday work. + At the beginning, tasks are enough. The team knows what needs to be done, who takes responsibility, and how the work is progressing. @@ -10,17 +15,10 @@ Over time, however, projects begin to grow. More initiatives appear. More people are involved. More parallel activities take place. -The work is no longer just a list of tasks, but a system of connected efforts that must be coordinated, structured, and managed on multiple levels. - -Naturally, the focus begins to shift: - -- from individual tasks to the overall structure -- from what we are doing today to where we are in the bigger picture -- from execution to managing scale and progress - -This is the moment when Project Management stops being a purely operational tool and becomes a management system. +Work is no longer just a list of tasks. +It becomes a system of connected efforts that need structure, coordination, and a clear sense of scale. -In @@name, this transition happens through **Project Groups**, **Project Areas**, and **Milestones** — tools that give projects shape, logic, and rhythm, without complicating the teams’ everyday work. +This is the moment when Project Management stops being purely operational — and becomes a management system. ## The structure that makes scale manageable From 6e504ca2efabec88bbf015a903b69a616457d1a5 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 15:08:06 +0200 Subject: [PATCH 05/31] Add Project Types, Case Categories & WIP limits subpage Introduces a new Project Management subpage explaining how Project Types, Case Categories, and WIP limits help manage flow, capacity, and focus across different types of work. --- .../types-case-categories-wip-limits.md | 299 ++++++++++++++++++ 1 file changed, 299 insertions(+) create mode 100644 features/work-management/types-case-categories-wip-limits.md diff --git a/features/work-management/types-case-categories-wip-limits.md b/features/work-management/types-case-categories-wip-limits.md new file mode 100644 index 00000000..2142f55c --- /dev/null +++ b/features/work-management/types-case-categories-wip-limits.md @@ -0,0 +1,299 @@ +# Project Types, Case Categories & WIP Limits + +## When work needs focus and flow + +As teams and projects grow, work naturally expands. +More tasks appear. More requests. More parallel activities. + +At a certain point, however, it becomes clear that cases alone are not enough. +The real challenge is no longer how much work is being done, but: + +- which work makes sense to take on right now +- how it is ordered and prioritized +- how it moves through the team without overload and bottlenecks + +This is where project management shifts from tracking work to managing **flow, capacity, and focus**. + +In @@name, this is achieved through **Project Types, Case Categories, and WIP limits** — tools that help work stay structured, understandable, and realistically planned *before execution even begins*. + +--- + +## Project Types – when projects have different natures + +Not all projects are the same. +And businesses know this very well. + +Some projects are client implementations. +Others are internal improvements. +Others still involve legal cases, product development, operational support, or research activities. + +The differences go beyond subject matter. +They affect how work is organized, what expectations exist, which stages are involved, how control is applied, and how progress is measured. + +When all these different projects are managed in the same way, familiar problems appear: + +- unnecessary fields and steps +- lack of clarity about what really matters +- processes that slow work down instead of supporting it + +That is why in Project Management in @@name, projects are not treated as generic objects. + +They are defined through **Project Types** — the tool that allows each project type to have its own logic, structure, and rules, aligned with how work is actually done. + +--- + +## Project Types – how the system understands what kind of project you are creating + +Before a project is created, the system asks a simple but extremely important question: + +**“What type of project is this?”** + +In @@name, this choice is not a formality. +It determines how the project will be structured, managed, and used in real work. + +A Project Type describes the nature of the project — whether it is a client implementation, an internal initiative, product development, a legal case, operational work, or something specific to your business. + +Based on the Project Type, the system knows: + +- what information is relevant for this kind of project +- which Case Categories are allowed +- what working logic should apply + +This allows projects to adapt to real working practices, instead of people adapting to a universal template. + +--- + +## Project Type vs. Project Group – similar concepts, different roles + +This is where confusion often arises, so the distinction matters. + +**Project Type** answers the question: +*“What kind of project is this?”* +It defines the identity of the project and how it works. + +**Project Group** answers the question: +*“Which projects belong to the same family and should share a common structure?”* +It is used when multiple projects need the same Areas and Milestones, without making them global for everyone. + +In short: + +- **Project Type** defines *what the project is* +- **Project Group** defines *shared structure across multiple projects* + +This combination allows project management to be both standardized and flexible. + +**How to choose correctly:** + +- If you want to define the nature of a project → **Project Type** +- If you want multiple projects to share the same structure → **Project Group** + +--- + +## Case Categories – how project type defines the way work is done + +Once a project has its type, the next logical question is: + +**“What kind of work happens inside this project?”** + +This is where **Case Categories** come into play in @@name. + +Case Categories define the types of tasks that can exist within a project and the working logic they carry. + +While the Project Type defines *what the project is*, +Case Categories define *what kind of work is performed inside it*. + +--- + +## From structure to real work + +In real life, different projects involve different types of activities: + +- analysis +- development +- coordination +- client communication +- approvals +- support +- internal improvements + +Case Categories allow these activities to be clearly distinguished, instead of being mixed into a single list of tasks. + +Each category can have its own logic, such as: + +- different fields +- different statuses +- different tracking approaches +- different working rules + +Tasks are no longer just “another Case”, +but part of a clear working model aligned with the project type. + +--- + +## How Project Types and Case Categories work together + +This is where the connection to Project Types becomes critical. + +Each Project Type can define: + +- which Case Categories are allowed +- what types of work make sense in this project +- what the expected workflow should be + +For example: + +- a **Client Implementation** project may include *Analysis, Configuration, Testing* +- an **Internal Operations** project may include *Requests, Improvements, Incidents* +- a **Legal / Advisory** project may include *Consultation, Drafting, Review* + +As a result: + +- teams work with familiar and meaningful categories +- projects have predictable structure +- management gains comparability and clarity + +--- + +## Better project management, stronger focus + +Case Categories do not complicate work — they **focus it**. + +Instead of all tasks looking the same across all projects: + +- teams know exactly what kind of work they are doing +- managers see which types of work consume the most capacity +- projects become easier to manage and analyze + +This naturally leads to the next step — +controlling workload and work flow through **WIP limits**. + +--- + +## WIP limits – when work flow has real boundaries + +Once we define what types of work are being done through Case Categories, the next — and much harder — question appears: + +**“How much work can we realistically handle at the same time?”** + +In many organizations, this question remains unanswered. +The result is familiar: + +- too many tasks “in progress” +- constant context switching +- a feeling of being busy, but slow progress + +This is exactly where **WIP limits** come into play in Project Management in @@name. + +--- + +## What WIP limits are + +WIP (Work In Progress) limits define the maximum number of Cases that can be in a given status or category at the same time. + +This is not a restriction on people. +It is a restriction on the system — so it reflects the team’s real capacity. + +In simple terms: + +- when the limit is reached +- new work does not automatically flow in +- existing work must be completed first + +--- + +## Why this matters for management + +WIP limits protect both teams and management from one of the most common traps in project work: + +**assigning more work than can realistically be completed.** + +With WIP limits: + +- planning becomes realistic +- workload becomes visible +- decisions are based on capacity, not assumptions + +Managers no longer assign work blindly, +but work with a clear signal of when the system is overloaded and when it can take on more. + +--- + +## Flow, not a task list + +WIP limits change how work is perceived. + +The focus shifts: + +- from *how many tasks we have* +- to *how tasks move* + +Work starts to be seen as a flow, not as accumulation. + +This leads to: + +- shorter lead times +- fewer blocked tasks +- a more sustainable working rhythm + +--- + +## WIP limits as part of the bigger picture + +In @@name, WIP limits do not exist in isolation. + +They work together with: + +- **Project Types** — defining project context +- **Case Categories** — defining types of work +- **User States** — showing movement and progress + +The system does not merely store a list of tasks. +It actively supports balanced distribution of work. + +--- + +## The real value + +WIP limits are not a methodology. +They are a **practical decision-making tool**. + +They help: + +- teams work on fewer things, but finish more +- managers plan without overloading people +- businesses achieve predictable outcomes + +Work does not slow down. +It simply starts flowing better. + +--- + +## Conclusion + +Project Types, Case Categories, and WIP limits work together as a management filter between intention and execution. + +They help businesses: + +- define what type of work is being done +- manage different work streams clearly and predictably +- plan based on real capacity, not urgency or pressure + +The result is not more control, but **better focus**. + +Teams understand what they are working on and why. +Management sees where capacity goes and how work moves. + +This transforms Project Management from a tracking tool into a system for better decisions. + +--- + +## 🔗 Navigation + +👉 **Back to the main topic:** +[Project Management in @@name](../project-management.md) + +👉 **Read more about:** +[Cases — where tasks turn into real work](./cases.md) + +👉 **Continue with:** +[Assignment Rules & User States — managing process and responsibility](./assignment-rules-user-states.md) From 14a980b1cdcbbd8f14e764dabe3104e78925bc30 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 15:57:18 +0200 Subject: [PATCH 06/31] Add Assignment Rules & User States subpage Adds a Project Management subpage explaining Assignment Rules and User States. Covers automated task distribution, shared status semantics, and process stability at scale. --- .../assignment-rules-user-states.md | 122 ++++++++++++++++++ 1 file changed, 122 insertions(+) create mode 100644 features/work-management/assignment-rules-user-states.md diff --git a/features/work-management/assignment-rules-user-states.md b/features/work-management/assignment-rules-user-states.md new file mode 100644 index 00000000..d8531031 --- /dev/null +++ b/features/work-management/assignment-rules-user-states.md @@ -0,0 +1,122 @@ +# Assignment Rules & User States +## When project management becomes a process + +In @@name, **Assignment Rules** and **User States** transform work management from simple “organization and assignment” into a sustainable, repeatable process: + +- tasks (Cases) reach the right people through clear, predefined rules; +- statuses mean the same thing to everyone — teams, management, and reporting alike. + +--- + +## Why this matters + +Even when projects are well structured and tasks are clearly defined, everyday work inevitably raises questions such as: + +- Who takes ownership of this task? +- When is a task actually “ready,” and when is it just waiting? +- What does a specific status really mean in practice? +- How do we avoid manual assignment and constant clarifications? + +This is where project management moves from a plan to a predictable flow of work. + +--- + +## Key capabilities + +### 1) Assignment Rules — automated work distribution + +**Assignment Rules** define how and to whom new or updated Cases are assigned — without the need for manual intervention every time. + +Rules can be based on criteria such as: + +- project type +- case category +- project, project area, or project group +- other business-specific conditions + +The result is consistent routing of work to: + +- the right team, +- the right role, +- or a specific responsible person. + +This does not “replace the manager.” +It removes routine work and reduces the risk of missed tasks — especially in environments with a high volume of incoming work. + +**Where it delivers the most value:** + +- larger teams with multiple roles +- repetitive types of work +- incoming request flows and operational processes +- service and support models + +--- + +### 2) User States — a shared language for real progress + +Statuses often seem clear… until they mean different things to different people. +For example, “In progress” might mean: + +- active work is happening; +- “we’ll start soon”; +- “we’re waiting for information”. + +**User States** solve this by enabling: + +- clear, business-meaningful status definitions; +- workflows adapted to how the organization actually works; +- elimination of ambiguity around progress. + +User States are not just labels — they are a shared language between teams and management about what is really happening with a task. + +--- + +## How it works (high level) + +### Assignment Rules (high level) + +- When a Case is created or when key attributes change (e.g. project, category, area), the system evaluates the applicable rules. +- If a match is found, @@name routes the Case to a team, role, or specific owner based on the rule logic. +- Incoming work is distributed predictably, without bottlenecks caused by manual reassignment or clarification. + +### User States (high level) + +- User States define the “intermediate” business stages teams actually use (e.g. *Waiting for info*, *For review*, *Ready*). +- This makes progress measurable and comparable — equally understandable to the people doing the work and those monitoring results. + +--- + +## Use cases + +These tools are especially valuable for: + +- service and support teams +- organizations with a steady inflow of tasks +- teams with clearly separated roles and responsibilities +- companies that want process without micromanagement + *(control through rules, not constant manual assignment)* + +Whether for projects, services, or internal coordination, rules and states provide stability at scale and reduce dependency on individual people. + +--- + +## Business benefits + +By using Assignment Rules and User States, businesses gain: + +- less manual coordination and task routing +- faster response to new tasks (shorter time to ownership) +- clearer accountability — who is doing what, and in which real stage +- reduced operational noise and task “bouncing” +- a predictable way of working as teams grow and change + +--- + +**Back to the main topic:** +[Project Management in @@name](../project-management.md) + +**Read more about:** +[Project Types, Case Categories & WIP limits — managing flow and capacity](./types-case-categories-wip-limits.md) + +**Start from the foundation:** +[Cases — where tasks turn into real work](./cases.md) From 5132c6f7955bdb6fe9b5e300fcc31098380da58c Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 16:13:19 +0200 Subject: [PATCH 07/31] Update toc.yml --- features/work-management/toc.yml | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/features/work-management/toc.yml b/features/work-management/toc.yml index 21a041fb..1c18bc81 100644 --- a/features/work-management/toc.yml +++ b/features/work-management/toc.yml @@ -1,4 +1,17 @@ - name: Overview href: index.md -- name: Project Management (PM) + +- name: Project Management href: project-management.md + +- name: Cases + href: cases.md + +- name: Areas, Project Groups & Milestones + href: areas-project-groups-milestones.md + +- name: Project Types, Case Categories & WIP Limits + href: types-case-categories-wip-limits.md + +- name: Assignment Rules & User States + href: assignment-rules-user-states.md From b599fa8509dfcaade7eda523efeee87366b16613 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 16:42:20 +0200 Subject: [PATCH 08/31] Update toc.yml --- features/work-management/toc.yml | 5 ----- 1 file changed, 5 deletions(-) diff --git a/features/work-management/toc.yml b/features/work-management/toc.yml index 1c18bc81..9da77e4a 100644 --- a/features/work-management/toc.yml +++ b/features/work-management/toc.yml @@ -1,17 +1,12 @@ - name: Overview href: index.md - - name: Project Management href: project-management.md - - name: Cases href: cases.md - - name: Areas, Project Groups & Milestones href: areas-project-groups-milestones.md - - name: Project Types, Case Categories & WIP Limits href: types-case-categories-wip-limits.md - - name: Assignment Rules & User States href: assignment-rules-user-states.md From 8b7792368cb4c386b9060dbda282c821c9671d2f Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 17:01:57 +0200 Subject: [PATCH 09/31] Rename features/work-management/project-management.md to features/work-management/project-management/project-management.md --- .../{ => project-management}/project-management.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename features/work-management/{ => project-management}/project-management.md (100%) diff --git a/features/work-management/project-management.md b/features/work-management/project-management/project-management.md similarity index 100% rename from features/work-management/project-management.md rename to features/work-management/project-management/project-management.md From 1ee53c64a8cb162976348f1c24d514ac7336311f Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 17:08:45 +0200 Subject: [PATCH 10/31] Rename features/work-management/areas-project-groups-milestones.md to features/work-management/project-management/areas-project-groups-milestones.md --- .../{ => project-management}/areas-project-groups-milestones.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename features/work-management/{ => project-management}/areas-project-groups-milestones.md (100%) diff --git a/features/work-management/areas-project-groups-milestones.md b/features/work-management/project-management/areas-project-groups-milestones.md similarity index 100% rename from features/work-management/areas-project-groups-milestones.md rename to features/work-management/project-management/areas-project-groups-milestones.md From 23518a465e8688fc645429fdef6f82c44aabffe6 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 17:09:06 +0200 Subject: [PATCH 11/31] Rename features/work-management/cases.md to features/work-management/project-management/cases.md --- features/work-management/{ => project-management}/cases.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename features/work-management/{ => project-management}/cases.md (100%) diff --git a/features/work-management/cases.md b/features/work-management/project-management/cases.md similarity index 100% rename from features/work-management/cases.md rename to features/work-management/project-management/cases.md From 482a991c836d540b1284a73365abf921a9937d3a Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 17:10:10 +0200 Subject: [PATCH 12/31] Rename features/work-management/types-case-categories-wip-limits.md to features/work-management/project-management/types-case-categories-wip-limits.md --- .../{ => project-management}/types-case-categories-wip-limits.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename features/work-management/{ => project-management}/types-case-categories-wip-limits.md (100%) diff --git a/features/work-management/types-case-categories-wip-limits.md b/features/work-management/project-management/types-case-categories-wip-limits.md similarity index 100% rename from features/work-management/types-case-categories-wip-limits.md rename to features/work-management/project-management/types-case-categories-wip-limits.md From 2ea81dabb12146f97cdb79c981df37f6cd8430f1 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 17:11:53 +0200 Subject: [PATCH 13/31] Rename features/work-management/assignment-rules-user-states.md to features/work-management/project-management/assignment-rules-user-states.md --- .../{ => project-management}/assignment-rules-user-states.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename features/work-management/{ => project-management}/assignment-rules-user-states.md (100%) diff --git a/features/work-management/assignment-rules-user-states.md b/features/work-management/project-management/assignment-rules-user-states.md similarity index 100% rename from features/work-management/assignment-rules-user-states.md rename to features/work-management/project-management/assignment-rules-user-states.md From a533d3e53ef1a5e4acee960270bef67b537c7bf1 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 17:36:35 +0200 Subject: [PATCH 14/31] Rename project-management.md to index.md --- .../project-management/{project-management.md => index.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename features/work-management/project-management/{project-management.md => index.md} (100%) diff --git a/features/work-management/project-management/project-management.md b/features/work-management/project-management/index.md similarity index 100% rename from features/work-management/project-management/project-management.md rename to features/work-management/project-management/index.md From 0117b3494adcb9320c8a7bd72cd92da7540150c6 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 17:44:02 +0200 Subject: [PATCH 15/31] Create toc.yml --- features/work-management/project-management/toc.yml | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 features/work-management/project-management/toc.yml diff --git a/features/work-management/project-management/toc.yml b/features/work-management/project-management/toc.yml new file mode 100644 index 00000000..f1953df8 --- /dev/null +++ b/features/work-management/project-management/toc.yml @@ -0,0 +1,10 @@ +- name: Overview + href: index.md +- name: Cases + href: cases.md +- name: Areas, Project Groups & Milestones + href: areas-project-groups-milestones.md +- name: Project Types, Case Categories & WIP Limits + href: types-case-categories-wip-limits.md +- name: Assignment Rules & User States + href: assignment-rules-user-states.md From d70f9e8179f08390dcf6683eff96395db2017eec Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 17:47:25 +0200 Subject: [PATCH 16/31] Update Work Management TOC to include Project Management section Link Project Management section with subpages via dedicated toc.yml and index.md --- features/work-management/toc.yml | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/features/work-management/toc.yml b/features/work-management/toc.yml index 9da77e4a..6a35a6c0 100644 --- a/features/work-management/toc.yml +++ b/features/work-management/toc.yml @@ -1,12 +1,5 @@ - name: Overview href: index.md - name: Project Management - href: project-management.md -- name: Cases - href: cases.md -- name: Areas, Project Groups & Milestones - href: areas-project-groups-milestones.md -- name: Project Types, Case Categories & WIP Limits - href: types-case-categories-wip-limits.md -- name: Assignment Rules & User States - href: assignment-rules-user-states.md + href: project-management/toc.yml + topicHref: project-management/index.md From 2d65fe85fdc5dbaf544ee00cb1c50d371717cc91 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 17:54:41 +0200 Subject: [PATCH 17/31] Updated links in index.md --- features/work-management/project-management/index.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/features/work-management/project-management/index.md b/features/work-management/project-management/index.md index 5a66ad46..dbf52331 100644 --- a/features/work-management/project-management/index.md +++ b/features/work-management/project-management/index.md @@ -313,8 +313,9 @@ You can explore and experience the powerful Project Management module in @@name It’s simple. -Just follow this guide to log into our publicly available test instance of @@name — **no registration required**: +Just follow this guide to log into our publicly available test instance of @@name — no registration required: -**Project Management in @@name — Try now without registration** +[Project Management in @@name — Try now without registration](https://express-demo.my.erp.net/cl/tiles) + +[Access credentials — Use these to log in](~/information/try-out-erp-net-express-crm.md) -**Access credentials** — Use these to log in. From 9cdd8c280b6ec866f31f90c466bda8b57146fa7b Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 17:59:24 +0200 Subject: [PATCH 18/31] Updated links in areas-project-groups-milestones.md --- .../project-management/areas-project-groups-milestones.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/features/work-management/project-management/areas-project-groups-milestones.md b/features/work-management/project-management/areas-project-groups-milestones.md index c97dce27..f4b34631 100644 --- a/features/work-management/project-management/areas-project-groups-milestones.md +++ b/features/work-management/project-management/areas-project-groups-milestones.md @@ -135,10 +135,10 @@ Whether it is a short initiative or a long-term program, the approach remains th ## Continue exploring Project Management **Back to the previous topic:** -[Cases – tasks as real work](https://info.erp.net/features/work-management/project-management/cases.html) +[Cases — where tasks turn into real work](cases.md) **Read next:** -[Types, Case Categories, and WIP limits — managing workflow and flow control](https://info.erp.net/features/work-management/project-management/types-case-categories-wip-limits.html) +[Project Types, Case Categories & WIP Limits — managing workflow and flow control](types-case-categories-wip-limits.md) **Back to the main topic:** -[Project Management in @@name](https://info.erp.net/features/work-management/project-management.html) +[Project Management in @@name](index.md) From d77977dcaaf75c71e50fe4ddd4ff7a4f3b2f1803 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 18:03:46 +0200 Subject: [PATCH 19/31] Updated links in assignment-rules-user-states.md --- .../project-management/assignment-rules-user-states.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/features/work-management/project-management/assignment-rules-user-states.md b/features/work-management/project-management/assignment-rules-user-states.md index d8531031..4e5cb748 100644 --- a/features/work-management/project-management/assignment-rules-user-states.md +++ b/features/work-management/project-management/assignment-rules-user-states.md @@ -112,11 +112,14 @@ By using Assignment Rules and User States, businesses gain: --- +## Continue exploring Project Management + **Back to the main topic:** -[Project Management in @@name](../project-management.md) +[Project Management in @@name](index.md) **Read more about:** -[Project Types, Case Categories & WIP limits — managing flow and capacity](./types-case-categories-wip-limits.md) +[Project Types, Case Categories & WIP Limits — managing flow and capacity](types-case-categories-wip-limits.md) **Start from the foundation:** -[Cases — where tasks turn into real work](./cases.md) +[Cases — where tasks turn into real work](cases.md) + From c92a0a732033d82569d956baa7df7277d2d58de0 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 18:07:17 +0200 Subject: [PATCH 20/31] Updated links in cases.md --- features/work-management/project-management/cases.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/features/work-management/project-management/cases.md b/features/work-management/project-management/cases.md index 2dc0dbca..e1965886 100644 --- a/features/work-management/project-management/cases.md +++ b/features/work-management/project-management/cases.md @@ -191,6 +191,10 @@ Time tracking directly from the Case makes the connection between effort and res ## What’s next -👉 **Back to the main topic:** [Project Management in @@name](project-management.md) -👉 **Read more about:** [Areas, Project Groups, and Milestones — managing project structure and scale](areas-project-groups-milestones.md) +**Back to the main topic:** +[Project Management in @@name](index.md) + +**Read more about:** +[Areas, Project Groups, and Milestones — managing project structure and scale](areas-project-groups-milestones.md) + From 64bc048e60240439ed8e1ed6b559aa0cd130e11a Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Fri, 9 Jan 2026 18:21:49 +0200 Subject: [PATCH 21/31] Updated links in types-case-categories-wip-limits.md --- .../types-case-categories-wip-limits.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/features/work-management/project-management/types-case-categories-wip-limits.md b/features/work-management/project-management/types-case-categories-wip-limits.md index 2142f55c..f8834fd1 100644 --- a/features/work-management/project-management/types-case-categories-wip-limits.md +++ b/features/work-management/project-management/types-case-categories-wip-limits.md @@ -287,13 +287,13 @@ This transforms Project Management from a tracking tool into a system for better --- -## 🔗 Navigation +## Continue exploring Project Management -👉 **Back to the main topic:** -[Project Management in @@name](../project-management.md) +**Back to the main topic:** +[Project Management in @@name](index.md) -👉 **Read more about:** -[Cases — where tasks turn into real work](./cases.md) +**Read more about:** +[Cases — where tasks turn into real work](cases.md) -👉 **Continue with:** -[Assignment Rules & User States — managing process and responsibility](./assignment-rules-user-states.md) +**Continue with:** +[Assignment Rules & User States — managing process and responsibility](assignment-rules-user-states.md) From b81ca0fbba82ddefcefb5d7e40fb1623e596bd90 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Mon, 12 Jan 2026 18:38:59 +0200 Subject: [PATCH 22/31] Updated links in index.md --- .../project-management/index.md | 44 ++++++++++++++++++- 1 file changed, 42 insertions(+), 2 deletions(-) diff --git a/features/work-management/project-management/index.md b/features/work-management/project-management/index.md index dbf52331..226226d2 100644 --- a/features/work-management/project-management/index.md +++ b/features/work-management/project-management/index.md @@ -201,7 +201,12 @@ With Project Areas: - the big becomes understandable - the complex becomes organized - teams see their part of the puzzle -- management sees the full picture +- management sees the full picture + +Project Areas bring clarity not by adding complexity, but by giving work a meaningful structure. + +To see how Areas, Project Groups, and Milestones work together to scale projects without losing focus, +continue with **[Areas, Project Groups & Milestones](./areas-project-groups-milestones.md)**. ### **3. You add the tasks — and the project begins to “breathe”** @@ -229,7 +234,12 @@ Each task has: The work is no longer scattered — everything becomes logical and traceable. -This is when the project begins to “breathe” — moving, evolving, living alongside the team. +Tasks are where planning turns into execution. +They carry responsibility, context, communication, and progress — all in one place. + +If you want to explore how Cases are designed to stay simple in daily work and powerful at scale, +read more in **[Cases — where tasks turn into real work](./cases.md)**. + ### **4. You track progress — without constant status meetings** @@ -257,6 +267,12 @@ Projects are not chaos — they are sequence. And regardless of scale — from a small initiative to a major transformation — the module keeps the process natural, transparent, and calm. +Structure alone is not enough when work grows. +Teams also need a way to decide what enters the system, how work is classified, and how much is “enough” at any given moment. + +This is where Project Types, Case Categories, and WIP limits help organizations balance focus and capacity. +Learn more in **[Project Types, Case Categories & WIP Limits](./types-case-categories-wip-limits.md)**. + --- ## Why Companies Choose This Way of Working @@ -271,6 +287,12 @@ Project Management in @@name gives you: - **Better control** — you understand not only what is done, but *why*. - **Universality** — no strict methodology required; works across industries. +As teams grow, consistency becomes just as important as clarity. +Who takes ownership, when work is truly ready, and what each status means — these answers must be shared and predictable. + +Assignment Rules and User States turn good intentions into a working process. +Explore how this works in **[Assignment Rules & User States](./assignment-rules-user-states.md)**. + --- ## How Businesses Use Project Management @@ -307,6 +329,24 @@ Annual plans, structural changes, strategic programs. --- +## Continue Exploring Project Management in @@name + +To fully understand how Project Management works in practice, explore its key building blocks: + +- **[Cases](./cases.md)** + Where tasks turn into real work, with ownership, history, and progress. + +- **[Areas, Project Groups & Milestones](./areas-project-groups-milestones.md)** + Structuring projects so teams and management share the same clear picture. + +- **[Project Types, Case Categories & WIP Limits](./types-case-categories-wip-limits.md)** + Managing flow, priorities, and capacity as work scales. + +- **[Assignment Rules & User States](./assignment-rules-user-states.md)** + Automating task ownership and creating a shared language for real progress. + +--- + ## Try Project Management in @@name Now You can explore and experience the powerful Project Management module in @@name yourself — see how projects become clearer, tasks more organized, and teamwork naturally aligned. From f14b1413c1dd2cbbad2fe61537c72c86a423625f Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Mon, 12 Jan 2026 18:40:15 +0200 Subject: [PATCH 23/31] Update index.md --- features/work-management/project-management/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/features/work-management/project-management/index.md b/features/work-management/project-management/index.md index 226226d2..cb430e2a 100644 --- a/features/work-management/project-management/index.md +++ b/features/work-management/project-management/index.md @@ -349,7 +349,7 @@ To fully understand how Project Management works in practice, explore its key bu ## Try Project Management in @@name Now -You can explore and experience the powerful Project Management module in @@name yourself — see how projects become clearer, tasks more organized, and teamwork naturally aligned. +You can explore and experience the Project Management module in @@name yourself — see how projects become clearer, tasks more organized, and teamwork naturally aligned. It’s simple. From 53a0d1eedc880b1e6fd979a9d5489476919f96bd Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Mon, 12 Jan 2026 18:51:59 +0200 Subject: [PATCH 24/31] Update image in index.md Image Cases was uploaded --- features/work-management/project-management/index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/features/work-management/project-management/index.md b/features/work-management/project-management/index.md index cb430e2a..606b67a5 100644 --- a/features/work-management/project-management/index.md +++ b/features/work-management/project-management/index.md @@ -240,6 +240,9 @@ They carry responsibility, context, communication, and progress — all in one p If you want to explore how Cases are designed to stay simple in daily work and powerful at scale, read more in **[Cases — where tasks turn into real work](./cases.md)**. +project-management-case + +--- ### **4. You track progress — without constant status meetings** From c0d867b2f1064bae7dc828cd4a7ab204c55c54d8 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Sat, 31 Jan 2026 15:19:36 +0200 Subject: [PATCH 25/31] Refine Project Management article: clearer wording MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reworked the remaining sections to reduce generic SaaS language and make benefits more concrete and verifiable. Improved narrative flow and readability while keeping the original ideas and messages. Reduced reliance on bullet-heavy formatting by converting many lists into prose. Added a compact “Why ERP.net” section focused on platform specifics: explainability, enforceable rules/constraints, traceability, consistent models, and predictable processes. Kept existing internal links and the “Try now” call-to-action intact. --- .../project-management/index.md | 289 +++++------------- 1 file changed, 79 insertions(+), 210 deletions(-) diff --git a/features/work-management/project-management/index.md b/features/work-management/project-management/index.md index 606b67a5..815130d0 100644 --- a/features/work-management/project-management/index.md +++ b/features/work-management/project-management/index.md @@ -2,27 +2,17 @@ ## Overview -In modern companies, ideas create movement. New products, improvements, client initiatives, internal processes — each of them requires coordination, clear steps, and visibility over progress. +In modern companies, ideas create movement. New products, improvements, client initiatives, and internal process changes all require coordination, clear steps, and visibility over progress. -Yet projects often scatter across emails, meetings, spreadsheets, and a dozen communication channels. -And sometimes something else happens — initiatives that “swim below the radar.” +Yet projects often end up scattered across emails, meetings, spreadsheets, and a dozen communication channels. And sometimes something else happens—initiatives “swim below the radar”. -Someone starts solving a problem, two or three colleagues join in, then another one... -Work is being done, time is being invested, people put in effort — but there is no official project, no record, no visibility. +Someone starts solving a problem, two or three colleagues join in, then another one. Work is being done, time is being invested, people put in real effort—yet there is no official project, no record, and no shared visibility. -These are the so-called *submarine projects* — the “hidden” projects of an organization. -They happen. -They consume resources. -But they are often neither seen, nor tracked, nor managed well. -And most importantly — leadership struggles to evaluate their impact or the workload they create. +These are the so-called submarine projects—the “hidden” projects of an organization. They happen, they consume resources, and they move forward in fragments, but they are rarely seen, tracked, or managed well. Most importantly, leadership struggles to evaluate their impact, understand the workload they create, or even know where they truly stand. -Regardless of the industry — manufacturing, services, distribution, commerce, technology — the question remains the same: +Regardless of the industry—manufacturing, services, distribution, commerce, technology—the question remains the same: “Where do we stand right now, and what comes next?” -**“Where do we stand right now, and what comes next?”** - -It would be wonderful if there were a place that gathers all of this — official projects, informal initiatives, ideas, tasks, progress, and resources. - -Fortunately, there is. +It would be wonderful if there were a single place that gathers everything—official projects, informal initiatives, ideas, tasks, progress, and resources—and turns it into a clear, shared picture. Fortunately, there is. project-management-home @@ -32,210 +22,108 @@ Fortunately, there is. ## There Is an Easier Way to Manage Your Projects -Imagine all company initiatives — big or small — gathered in one place. -A place where every idea receives structure, every task has its place, and every step is part of a logical sequence. - -A place where: +Imagine all company initiatives—big or small—gathered in one place. A place where every idea receives structure, every task has its place, and every step is part of a logical sequence. -- every step is clear — no time wasted in clarifications -- every task has an owner — responsibilities are visible -- every action has history — you know what happened and why -- progress is visible without asking anyone -- documents, files, and communication are organized and available when needed +In practice, that means fewer clarifications because steps are clear; visible responsibility because every task has an owner; real context because every action has history; and progress that can be understood without constantly asking for updates. It also means documents, files, and communication are organized and available when needed, not buried in email threads or “final version” folders. -This is not merely convenience. -It’s a way of working that gives: +This is not merely convenience. It’s a way of working that gives teams peace of mind, managers confidence, processes consistency, and results greater predictability. -- peace of mind to teams -- confidence to managers -- consistency to processes -- predictability to results +When everything lives in one place, projects start to move more naturally: people work in sync, resources are used more wisely, and initiatives don’t sink into “submarine” efforts—they become visible and traceable. -When everything lives in one place, projects start to move more naturally. -People work in sync. -Resources are used more wisely. -Initiatives don’t sink into “submarine” efforts — they become visible and traceable. - -This clarity and order is exactly what **Project Management in @@name** delivers — helping organizations turn ideas into real outcomes without complicating their processes. +This clarity and order is exactly what Project Management in @@name delivers—helping organizations turn ideas into real outcomes without complicating their processes. --- ## What Project Management in @@name is -Project Management in @@name is the core that connects people, ideas, and actions into a structured, traceable, and understandable flow of work. -Whether it’s client service, an internal initiative, product development, or coordination between teams — the module turns work into sequence, and sequence into results. +Project Management in @@name is the core that connects people, ideas, and actions into a structured, traceable, and understandable flow of work. Whether it’s client service, an internal initiative, product development, or coordination between teams, the module turns work into a sequence—and that sequence into results. -At its foundation stand several key components that naturally work together: +At its foundation are several components that work together naturally. ### **Projects — the framework of every initiative** -Each project in @@name acts as a “container” that gathers everything related to an initiative: - -- goals -- participants -- expected outcomes -- stages -- relevant information -- documents -- communication - -This is the central point that provides an overview of the work — whether it’s a major corporate project or a small internal effort with just a few steps. +Each project in @@name acts as a “container” that gathers everything related to an initiative: goals, participants, expected outcomes, stages, relevant information, documents, and communication. This creates a single point of reference that makes the work easier to understand and manage—whether it’s a major corporate effort or a small internal improvement with just a few steps. ### **Project Areas — organizing work into meaningful sections** -A large project becomes far more comprehensible when divided into zones. -With **Project Areas**, you can structure the work by: - -- phases -- activity types -- business functions -- teams -- work streams +Even a well-defined project becomes harder to follow when everything lives in one long list. +Project Areas help you divide the work into clear, meaningful sections, so the big picture stays visible and the details remain easy to find. +You can structure Areas by phases, activity types, business functions, teams, or work streams—depending on how your organization thinks and works. -Examples include *Planning*, *Execution*, *Marketing*, *Communications*, *Finalization*. -This helps both large and small teams visualize the big picture without losing the details. +In practice, this could mean Areas such as Planning, Execution, Marketing, Communications, and Finalization. +The specific names are less important than the result: a shared structure that helps both large and small teams coordinate without confusion. ### **Tasks (Cases) — the concrete steps that move the project forward** -Real work happens in the details. +Real work happens in the details. In @@name, those details take shape as Tasks (Cases): clearly defined actions with an owner, a deadline, a current status, and the necessary context—description, related documents, and comments. -Each task is a clearly defined action: +As work grows, Tasks remain manageable because you can organize, filter, group, and track them in ways that match how teams actually operate. +The goal is simple: no important step gets lost, even when many people contribute and many things happen in parallel. -- what needs to be done -- who is responsible -- the deadline -- current status -- related documents or comments - -@@name allows you to organize, filter, group, and track all tasks so that no important step is ever lost — even in large projects with many contributors. ### **Documents and Files — everything in the right place** -No more searching for attachments in emails, old messages, or folders named *“Final version v5”*. -Documents, contracts, specifications, protocols, images, comments — everything lives inside the project. +Projects generate content: specifications, contracts, protocols, images, notes, and all the small pieces that teams rely on to move forward. When these files live in mail threads or scattered folders, progress slows down and context disappears. -This increases productivity and keeps context clear, even when the team grows or someone joins later. +In @@name, documents and files live inside the project, where they belong. +This keeps information close to the work, improves productivity, and makes onboarding easier when the team grows or someone joins later. ### **History and Communication — every action has context** -Every action — a new task, a status change, an uploaded file, a comment, or an update — is logged automatically. -This provides: - -- transparency -- traceability -- confidence that nothing gets lost +Project work is not just a series of tasks—it’s a sequence of decisions. +In @@name, the key actions within a project are logged automatically: new tasks, status changes, uploaded files, comments, and updates. +This gives the team transparency and traceability, and it reduces the risk of losing important context over time. -History becomes a guide — especially for long or multi-stage projects. +History becomes especially valuable in long-running or multi-stage projects, where understanding “what happened and why” is just as important as knowing “what happens next”. ### **Real-time Progress — a clear picture without meetings** -@@name visualizes what is completed, what’s upcoming, and where blockers exist. -Managers see movement across the project without status meetings, while contributors receive a natural rhythm and clear priorities. +@@name visualizes what is completed, what’s upcoming, and where blockers exist. +Managers can see movement across the project without constant status meetings, while contributors get a natural rhythm and clearer priorities—because progress is visible as part of the work, not something that has to be repeatedly reported --- ## One Logic, Many Industries -Because it is structured yet lightweight, Project Management works naturally in different business environments: +Project Management in @@name is designed around a simple idea: project work is a sequence of decisions and actions, and the system should make that sequence explicit and trackable. +This logic stays the same across very different environments—consulting (client implementations), manufacturing (new product launches), logistics (warehouse process optimization), marketing (campaigns), and administration (certifications and internal initiatives). -- consulting — *client implementation* -- manufacturing — *new product launch* -- logistics — *warehouse process optimization* -- marketing — *campaign* -- administration — *certification* or *internal initiative* - -The principle is always the same: -**Step by step, tasks lead to results.** -@@name makes each step lighter, clearer, and more visible. +The principle is always the same: **step by step, tasks lead to results**. @@name supports this by keeping the steps clear, the responsibility explicit, and the progress visible in a way that can be checked—without relying on “who remembers what”. --- ## How It Works — Told as a Real Process -Managing a project often seems daunting: many people, many tasks, many unknowns. -But in practice — and especially in @@name — the process is far more natural than it sounds. - -Imagine you’re starting a new initiative. It might be something big like preparing for a trade show, or something small like improving an internal process. What’s the first thing you do? +Project management can look daunting from the outside: many people, many tasks, many unknowns. +In practice, the work becomes manageable when it has a clear place to live, a shared structure, and a single way to track what is happening and why. +That’s the logic behind Project Management in @@name. ### **1. You give it a name — and the project finally has a “home”** -Every initiative starts as an idea: - -- “Let’s update the website.” -- “Let’s prepare a presentation for the client.” -- “Let’s develop a new product.” -- “Let’s organize a company event.” - -In @@name this idea becomes a **Project** — a protected space that gathers everything that will follow: +Every initiative starts as an idea: “Let’s update the website.” “Let’s prepare a presentation for the client.” “Let’s develop a new product.” “Let’s organize a company event.” -- description -- participants -- goals -- deadlines -- expected outcomes - -This is the moment the project is “born” — no longer just a conversation or an email. -It has a name, a beginning, a purpose. +In @@name, this idea becomes a **Project**—a defined workspace where the initiative is described and owned. +Instead of being spread across conversations and messages, the work gets a single reference point with participants, goals, deadlines, and expected outcomes. +From that moment on, the initiative is no longer “some work we’re doing”; it is something the organization can track, manage, and learn from. ### **2. You structure it — using Project Areas** -Once the project has its home, the natural question is: -**“How do we organize it so everyone understands it?”** - -This is where **Project Areas** shine. - -You can divide the work into: - -- Planning -- Execution -- Marketing -- Communications -- Delivery -- Technical Preparation -- Finalization +Once a project exists, the next question is straightforward: **how do we organize it so everyone understands it the same way?** -Or anything that fits your workflow. +This is what **Project Areas** provide: a shared structure that helps people locate their work without losing the big picture. +Depending on the initiative, Areas can follow phases (Planning, Execution, Finalization), functions (Marketing, Communications), teams, work streams, or any structure that matches how the organization actually operates. -With Project Areas: - -- the big becomes understandable -- the complex becomes organized -- teams see their part of the puzzle -- management sees the full picture - -Project Areas bring clarity not by adding complexity, but by giving work a meaningful structure. +The important part is not the naming—it’s the outcome: work is grouped meaningfully, responsibility is easier to coordinate, and progress can be reviewed per Area rather than through one long, mixed list. To see how Areas, Project Groups, and Milestones work together to scale projects without losing focus, continue with **[Areas, Project Groups & Milestones](./areas-project-groups-milestones.md)**. ### **3. You add the tasks — and the project begins to “breathe”** -Projects move through small, concrete actions. -In @@name these actions are **Tasks (Cases)** — clearly defined steps leading to progress. - -Examples: - -- Prepare schedule -- Draft presentation -- Confirm specifications -- Send samples -- Review offer -- Test component -- Upload final document - -Each task has: +Projects advance through small, concrete actions. In @@name, these actions are **Tasks (Cases)**—work items with an owner, a deadline, a status, and the necessary context (description, files, and comments), linked to the relevant Project Area. -- an owner -- a deadline -- a description -- a status -- attached files and comments -- a link to its Project Area - -The work is no longer scattered — everything becomes logical and traceable. - -Tasks are where planning turns into execution. -They carry responsibility, context, communication, and progress — all in one place. +Instead of work living in personal notes or scattered messages, tasks become explicit and traceable. +A team can see what is being done, what is waiting, and what is blocked—not as an opinion, but as the current documented state of the work. If you want to explore how Cases are designed to stay simple in daily work and powerful at scale, read more in **[Cases — where tasks turn into real work](./cases.md)**. @@ -246,89 +134,70 @@ read more in **[Cases — where tasks turn into real work](./cases.md)**. ### **4. You track progress — without constant status meetings** -Progress is visible throughout the module: +As the team works, @@name keeps the project status readable: what is completed, what comes next, where blockers exist, who is actively involved, and what affects milestones and deadlines. +This reduces the need to “collect information” through constant check-ins, because the state of the work is visible as a result of the work itself. -- what is completed -- what is upcoming -- where blockers exist -- who is actively involved -- what affects milestones and deadlines +--- -@@name updates this in real time as people work. -No more *“What’s happening here?”* emails or emergency sync meetings. +## The Result? Work Flows Smoothly -Instead of gathering information — -you simply **see** it. +Projects are not chaos—they are sequence. @@name helps you keep that sequence visible and consistent: what was planned, what is being executed, what changed, and what happens next. +This remains true whether you are coordinating a small internal improvement or running a major cross-team initiative. ---- +As work grows, structure alone is not enough. Teams also need a way to decide what enters the system, how work is classified, and how much work-in-progress is acceptable at any given moment. +This is where Project Types, Case Categories, and WIP limits help organizations balance focus and capacity. -## The Result? Work Flows Smoothly +Learn more in **[Project Types, Case Categories & WIP Limits](./types-case-categories-wip-limits.md)**. + +--- -Projects are not chaos — they are sequence. -@@name helps you see that sequence, organize it, and follow it with ease. +## Why ERP.net -And regardless of scale — from a small initiative to a major transformation — -the module keeps the process natural, transparent, and calm. +Project Management in @@name is not an isolated “PM tool” added on top of the organization. +It is part of a platform designed around explicit models, enforceable rules, and traceable processes. -Structure alone is not enough when work grows. -Teams also need a way to decide what enters the system, how work is classified, and how much is “enough” at any given moment. +In practice, that means the system is built to be **explainable**: you can follow what happened, when it happened, and why the current state is what it is. It also means the platform relies on **rules and constraints** to keep work consistent—so the process is not “whatever each team member happens to do”, but a shared, predictable way of moving tasks forward. -This is where Project Types, Case Categories, and WIP limits help organizations balance focus and capacity. -Learn more in **[Project Types, Case Categories & WIP Limits](./types-case-categories-wip-limits.md)**. +Because ERP.net uses **consistent models and shared concepts** across the platform, work management can stay aligned with the rest of the organization’s logic. +The goal is simple and verifiable: fewer contradictions, less ambiguity, and a process that remains understandable even as teams grow and projects multiply. --- ## Why Companies Choose This Way of Working -Projects exist everywhere. The difference lies in how we manage them. +Projects exist everywhere. The difference lies in whether an organization can see its work as a coherent system, or only as fragments scattered across tools and conversations. -Project Management in @@name gives you: +Project Management in @@name helps teams reduce the effort of coordination by making responsibility explicit (who owns what), progress observable (what is done and what is blocked), and context durable (files, discussions, and changes stay attached to the work). It also helps management evaluate workload and impact based on what the system records—not on ad-hoc summaries prepared for meetings. -- **Peace of mind** — you know what’s happening without extra meetings. -- **Transparency** — everyone sees progress and knows what to do. -- **Less chaos** — documents, comments, tasks — everything is organized. -- **Better control** — you understand not only what is done, but *why*. -- **Universality** — no strict methodology required; works across industries. +As teams grow, consistency becomes just as important as clarity. Who takes ownership, when work is truly ready, and what each status means—these answers must be shared and predictable. Assignment Rules and User States support that by turning a “we should do it this way” intention into a repeatable working process. -As teams grow, consistency becomes just as important as clarity. -Who takes ownership, when work is truly ready, and what each status means — these answers must be shared and predictable. - -Assignment Rules and User States turn good intentions into a working process. Explore how this works in **[Assignment Rules & User States](./assignment-rules-user-states.md)**. --- ## How Businesses Use Project Management -Examples common to almost every company: - -### **Preparing for a trade show** -Marketing + logistics + production. +**Preparing for a trade show.** Marketing, logistics, and production work in parallel; tasks, files, and decisions stay in one project, structured by Areas. -### **Implementing a product for a client** -Steps: requirements → configuration → testing → training → support. +**Implementing a product for a client.** Requirements → configuration → testing → training → support become a visible sequence, not a chain of disconnected handovers. -### **Launching a new product** -Design → development → testing → marketing → sales enablement. +**Launching a new product.** Design, development, testing, marketing, and sales enablement can be coordinated with clear ownership and status. -### **Internal initiatives** -Warehouse optimization, process improvements, certifications, ISO projects. +**Internal initiatives.** Warehouse optimization, process improvements, certifications, and ISO projects benefit from traceability—especially when they stretch across months and multiple stakeholders. -### **Corporate goals and planning** -Annual plans, structural changes, strategic programs. +**Corporate goals and planning.** Annual plans, structural changes, and strategic programs become easier to track when the work is broken down into projects with explicit milestones and responsibilities. -### **Any work requiring coordination across many people** -@@name turns complexity into sequence. +**Any work requiring coordination across many people.** @@name turns complexity into a sequence that can be followed and managed. --- ## Business Benefits — Real, Measurable, Tangible -- Better organization — everything has its place -- Clearer focus — teams work with confidence -- Shorter timelines — less clarifying, more doing -- Better communication — history, comments, documents -- Better accountability — see the impact, not just the tasks +Better organization comes from keeping tasks, documents, and communication in context instead of scattered. +Clearer focus comes from shared structure and visible ownership. +Shorter timelines come from reducing clarifications and rework, because current status and blockers are visible. +Better communication comes from having history and decisions attached to the work itself. +Better accountability comes from being able to evaluate outcomes and workload based on what the system records, not only on what is reported. --- From 9067a4cbb42803350999bcb58a3702f612bef968 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Sat, 31 Jan 2026 17:06:15 +0200 Subject: [PATCH 26/31] =?UTF-8?q?Rewrite=20=E2=80=9CCases=E2=80=9D=20subpa?= =?UTF-8?q?ge:=20less=20generic=20SaaS=20tone=20+=20clearer=20structure?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Rewrote the “Cases” sub-article for Project Management in @@name to align with info.erp.net style and structure. Reduced generic SaaS phrasing by grounding claims in concrete, checkable mechanisms (ownership, state, history, context, time markers). Consolidated overlapping sections to remove repetition while preserving all key ideas and messages. Kept all section headings unchanged and ensured markdown line-break rules are followed (sentence-per-line, explicit paragraph breaks). Added a compact “Why ERP.net” section highlighting platform specifics: explainability, enforceable rules/states, traceability, and consistent concepts across @@name --- .../project-management/cases.md | 205 +++++++++--------- 1 file changed, 97 insertions(+), 108 deletions(-) diff --git a/features/work-management/project-management/cases.md b/features/work-management/project-management/cases.md index e1965886..a2196e35 100644 --- a/features/work-management/project-management/cases.md +++ b/features/work-management/project-management/cases.md @@ -1,191 +1,180 @@ # Cases -## Where tasks turn into real work -At the core of every project activity are concrete tasks. -They define what needs to be done, by whom, within what timeframe, and in what context. +## Where tasks turn into real work -The clearer these tasks are defined and managed, the more predictable the work becomes — both for teams and for management. -That is why task management is not an operational detail, but a key element of project management as a whole. +At the core of every project are concrete tasks. +They define what needs to be done, by whom, within what timeframe, and in what context. +When tasks are defined and managed consistently, teams spend less time clarifying ownership and current status. +Management can evaluate workload and progress based on what is actually recorded, rather than on ad‑hoc updates. -Many organizations sense this intuitively — work gets done, but context, decisions, and progress are often managed across multiple tools. +Many organizations feel this challenge intuitively. +Work gets done, but context, decisions, and progress end up distributed across multiple tools. +Later, it becomes surprisingly hard to answer simple questions like why a decision was made, what changed, and who agreed on what. --- ## The core instrument: Cases in Project Management in @@name In Project Management in @@name, work execution is organized through **Cases**. -They are the place where tasks are planned, taken on, executed, and tracked — without losing context along the way. +A Case is where a task is planned, taken on, executed, and tracked, while keeping the relevant context attached to the work. -Each Case brings together everything needed for real work: -who is responsible, what the priority is, what the current status is, what has been discussed, which documents are involved, and how the process has evolved over time. +A Case brings together what a team typically needs to execute responsibly. +It keeps ownership, priority, current state, discussion, related documents and files, and the history of changes over time in one place. +This turns a Case into a practical unit of work that the team can coordinate around and the organization can review later with clarity. -This transforms a Case from a simple task into a complete unit of work — one that can be managed, analyzed, and extended. - -The way Cases are designed allows teams to start with minimal information when needs are simple, and gradually add structure, detail, and control as projects grow more complex and requirements increase. -As a result, Cases remain comfortable for everyday operational work while being fully suitable for large-scale projects with extensive coordination and business-level accountability. +Cases are usable from day one. +A team can start with only what is necessary, such as a title and an owner. +As requirements grow, the Case can grow with them by adding deadlines, user states, estimates, links to related work, or additional detail when the process actually needs it. +This keeps Cases comfortable for everyday operational tasks, while still supporting complex project environments where traceability and accountability matter. --- ## What a Case represents in @@name -A Case in @@name is not just a task to be checked off. -It is a focal point of work — the place where an intention becomes real execution. - -A Case can start and finish very simply — with just a name and an owner. -Exactly as much as is needed to move work forward. +A Case in @@name is not just a checkbox in a list. +It is the point where an intention becomes execution, with a defined owner and a visible state. -As work evolves, the Case can naturally grow with it. -Priority, deadlines, statuses, descriptions, notes, and links to other tasks can be added — only when the business process requires it. +A Case can be lightweight when the work is simple. +It can start with just a name and an owner, exactly as much as is needed to begin. +As the work evolves, priority, deadlines, statuses, notes, dependencies, and related work can be added when the business process requires them. -A Case brings together in one place: - -- responsibility and deadlines -- current state and full history -- internal discussions and comments directly related to the work -- files and documents used in the process - -This way, a task is never “bare” — it always carries its context. +Most importantly, a Case is never bare. +Ownership and deadlines sit next to the current state and the full history. +Discussions, decisions, and clarifications remain attached to the work, instead of being lost in email threads or chat logs. +Files and documents used during execution stay easy to find later, in the same place where the task lives. --- ## A workspace, not just a record -A Case in @@name is designed as a workspace, not a static object. +A Case in @@name is designed as a workspace for execution, not a static object stored somewhere for reference. -Within a Case, users can: +Within a Case, users can track time while working. +They can define estimated time when planning is required. +They can use Story Points when the team prefers that approach. +When work is iterative, a Case can also be associated with a Sprint. -- track time directly while working -- define estimated time when planning is required -- use Story Points when the team works that way -- associate the Case with a Sprint when work is iterative +Cases can be linked to the relevant business and organizational context as well. +A Case can be connected to a specific project. +It can be associated with a Social Group when the work concerns a particular team. +It can be linked to a Party, such as a customer, partner, or counterparty, independently of who the Case is assigned to. +This helps teams see work not only as who does what, but also for whom and in what business context. -A Case can also be linked: +project-management-case1 -- to a specific project -- to a Social Group when the task concerns a particular team -- to a Party (customer, partner, or counterparty), independently of who the task is assigned to - -This allows tasks to be viewed not only as “who does what”, but also **for whom** and **in what business context**. +*A Case in @@name keeps execution, context, files, communication, and time in one place — so the work remains explainable later.* --- ## Control over time and state — when it is needed -Cases support different time-related states, such as readiness, waiting, or completion moments. -These markers make it possible to analyze how work actually flows, without adding burden to daily operations. - -By default, tasks move through standard states such as **Backlog**, **In Progress**, **Waiting**, or **Closed**. -When a business follows a more specific process, these states can be extended and adapted through custom **User States**. +Cases support time-related markers such as readiness, waiting, or completion moments. +These markers make flow visible. +They help teams and managers see where work moves smoothly, where it waits, and where delays accumulate, without turning daily execution into a heavy reporting exercise. -The system does not impose a model — it follows it. +By default, Cases move through standard states such as Backlog, In Progress, Waiting, or Closed. +When a business follows a more specific workflow, states can be extended and adapted through custom **User States**. +The goal is not to impose a methodology. +The goal is to make the team’s real process explicit and shared, so it remains understandable even as more people join the work. --- ## Simplicity on the surface, depth underneath -The most important aspect of Cases is that no one is required to use everything at once. -Teams can work in a light and intuitive way, while the system remains ready to support more structure, control, and accountability whenever needed. - -This combination — ease of use with real depth — makes Cases suitable both for everyday tasks and for complex project environments. +Cases do not require heavy setup to be useful. +Teams can work with the minimum they need today, and add structure only when the process demands it tomorrow. +This keeps the same Case model usable for quick operational execution and for larger-scale coordination with reviewable history. --- ## Context and communication — part of the task itself -One of the greatest strengths of Cases is that all communication can take place directly within the task. - -Discussions, decisions, and clarifications do not get lost in emails or chats — they remain part of the Case history. -This provides clear answers to questions such as: - -- why a certain decision was made -- what was discussed -- who was involved - -Context stays with the work — even as people or priorities change. +Cases keep communication where it matters: inside the task. +When a Case is revisited weeks or months later, the discussion and decisions are still there, next to the files and the state history. +That continuity reduces rework, because the team does not need to reconstruct context from memory. --- ## Hierarchy and focus in execution -Cases allow tasks to be managed hierarchically. +Cases support hierarchical execution through subcases. +This allows teams to break down larger activities into logical steps. +It also helps distribute responsibilities clearly while preserving the relationship between an overall goal and the concrete actions required to achieve it. -A Case can contain subcases, making it possible to: - -- break down larger activities into logical steps -- clearly distribute responsibilities -- preserve the connection between overall goals and concrete actions - -This is especially valuable in more complex projects and cross-team coordination. +For cross-team projects, hierarchy protects focus. +Teams can coordinate on smaller, owned parts of the work without losing their connection to the bigger outcome. --- ## When work has a clear entry point and a clear flow — Backlog and Kanban -In real work, tasks do not arrive neatly ordered. -Ideas, requests, improvement proposals, issues, and commitments constantly emerge — from customers, teams, and management. +In real organizations, tasks do not arrive neatly ordered. +Requests, incidents, improvements, and commitments appear continuously from customers, teams, and management. +That is why in Project Management in @@name, Cases typically begin in the **Backlog**. +The Backlog is where upcoming work is collected, organized, and prioritized. +It answers the practical question “What’s next?” without forcing immediate execution or creating artificial urgency. -That is why in Project Management in @@name, **Cases begin their life in the Backlog** — the place where all upcoming work is collected, organized, and prioritized. -The Backlog answers the question *“What’s next?”* without creating pressure or a sense of overload. +Planning remains a team responsibility. +Teams decide which Cases from the Backlog are ready to be taken on, when, and with what priority. +From there, **Kanban** visualization helps turn planning into execution by making flow visible across states, from idea and preparation, through work in progress, to completion. -How this work is planned and organized is entirely in the hands of the teams. -Users decide which Cases from the Backlog are ready to be taken on, when, and with what priority — turning planning into an active process rather than a static list. +This visibility helps teams and managers see what is in progress, what is waiting for input or decisions, what is planned next, and what is completed. +In this sense, Kanban in @@name is not only a visual view. +It is a way to keep work-in-progress and waiting time observable, so priorities and capacity can be managed with fewer assumptions. -From there, **Kanban visualization turns planning into action**. -With an intuitive drag-and-drop interface, Cases move between statuses — from idea, through preparation and execution, to completion — directly from the visual view. +The Backlog secures the intake of work. +Kanban helps manage its flow. +Cases are where execution, context, and history stay together in a clear business context. -This allows teams to see at a glance: +--- -- what is currently in progress -- which Cases are waiting for input or decisions -- which Cases are planned -- which Cases are completed +## Why ERP.net -Kanban in @@name is more than visualization. -It is a tool for focus, balance, and consistency — a way for work to move forward without losing control over priorities. +Cases in @@name are built on a platform that emphasizes explicit models, enforceable rules, and traceable processes. -The Backlog secures the **input** of work. -Kanban manages its **flow**. -And Cases are where all of this happens — in a clear business context. +This translates into practical, checkable outcomes. +Work remains **explainable** because a Case keeps state, history, discussion, and files together, so the current situation can be understood from what is recorded. +Processes remain **predictable** because teams can make workflow explicit through states and rules, rather than relying on informal habits. +Because @@name uses **consistent concepts across the platform**, Cases can stay connected to projects, teams, and business parties without losing meaning as the organization grows. --- ## Business benefits: what the business gains from Cases -When tasks are managed through Cases in @@name, the business gains far more than an organized task list. +When tasks are managed through Cases in @@name, the business gains more than an organized list. +It gains a work record that remains readable over time. -### Clear responsibility and traceability -Every task has an owner, a history, and context — decisions and actions remain visible over time. +**Clear responsibility and traceability.** +Ownership is explicit, state is visible, and changes remain reviewable through the Case history. -### Better coordination between teams -People work in a shared space where communication, files, and progress are transparent to all involved. +**Better coordination between teams.** +Communication, files, and progress stay attached to the same work item, reducing misunderstandings and duplicate effort. -### Less operational friction -Documents, discussions, and time tracking happen where work is done — without unnecessary switching between tools. +**Less operational friction.** +Time tracking, documents, and discussions happen where the work happens, minimizing tool-switching and context loss. -### Predictable and controllable execution -Progress is visible, delays are detected early, and management decisions are based on real information. +**Predictable and controllable execution.** +Progress and waiting states are visible, delays can be detected earlier, and decisions can be based on recorded reality rather than informal status summaries. --- ## Applicability: where Cases work best -Cases are especially valuable where work is not one-off, but evolves over time and involves people, decisions, and context. +Cases are especially valuable where work evolves over time and involves people, decisions, and context, not just a one-off action. -### Client and project work -When multiple tasks are performed for a client or project, each Case can represent a specific activity — with owner, deadline, discussion, and documents. -This keeps the full history of work traceable: what was requested, agreed upon, and delivered. +**Client and project work.** +Requests, agreements, delivery files, and decisions remain attached to the Case, making the full path from request to outcome traceable. -### Internal initiatives and improvements -Cases bring the same clarity to internal work as to client projects. -Ideas and improvements do not get lost — they become concrete tasks with visible progress. +**Internal initiatives and improvements.** +Ideas do not get lost. +They become Cases with ownership and visible state, so progress can be reviewed without reconstructing history from meetings and messages. -### Operational coordination across teams -When multiple roles or departments are involved, the Case becomes a shared point of work. -Everyone sees the current state, participates in discussion, and works with the same information. +**Operational coordination across teams.** +When several roles or departments are involved, the Case becomes the shared point of work. +Everyone sees the same state, participates in the same discussion, and works with the same context. -### Services and time-accountable activities -Cases are a natural choice when it is important to know how much time was spent, on which task, and for what outcome. -Time tracking directly from the Case makes the connection between effort and results fully transparent. +**Services and time-accountable activities.** +When it matters how much time was spent, on which task, and for what outcome, time tracking directly from the Case keeps effort and results connected and reviewable. --- From 3b7960f9df78360fdc56af81a9f37bf9ee43da32 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Sat, 31 Jan 2026 17:41:36 +0200 Subject: [PATCH 27/31] =?UTF-8?q?Rewrite=20=E2=80=9CProject=20Types,=20Cas?= =?UTF-8?q?e=20Categories=20&=20WIP=20Limits=E2=80=9D=20subpage=20for=20in?= =?UTF-8?q?fo.erp.net?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Rewrote the sub-article to align with info.erp.net style while preserving the original structure and section headings. Reduced generic SaaS phrasing by grounding claims in concrete, checkable mechanisms (type-driven context, category-based work classification, explicit WIP boundaries). Clarified the relationship between Project Types, Project Groups, and Case Categories with tighter, more practical explanations. Improved narrative flow and readability using sentence-per-line Markdown formatting and clean paragraph breaks. Added a compact “Why ERP.net” section emphasizing platform specifics: explicit models, enforceable rules, traceability, and predictable processes in @@name. --- .../types-case-categories-wip-limits.md | 281 +++++++----------- 1 file changed, 102 insertions(+), 179 deletions(-) diff --git a/features/work-management/project-management/types-case-categories-wip-limits.md b/features/work-management/project-management/types-case-categories-wip-limits.md index f8834fd1..cf03a24a 100644 --- a/features/work-management/project-management/types-case-categories-wip-limits.md +++ b/features/work-management/project-management/types-case-categories-wip-limits.md @@ -3,63 +3,42 @@ ## When work needs focus and flow As teams and projects grow, work naturally expands. -More tasks appear. More requests. More parallel activities. +More requests appear, more parallel activities start, and priorities change more often. +At that stage, Cases remain the place where work happens, but teams also need a way to shape *what enters the system*, *how work is classified*, and *how much can run in parallel without overload*. -At a certain point, however, it becomes clear that cases alone are not enough. -The real challenge is no longer how much work is being done, but: - -- which work makes sense to take on right now -- how it is ordered and prioritized -- how it moves through the team without overload and bottlenecks - -This is where project management shifts from tracking work to managing **flow, capacity, and focus**. - -In @@name, this is achieved through **Project Types, Case Categories, and WIP limits** — tools that help work stay structured, understandable, and realistically planned *before execution even begins*. +That is where project management shifts from tracking execution to managing flow, capacity, and focus. +In @@name, this is supported through Project Types, Case Categories, and WIP limits. +Together, they help work stay structured, understandable, and realistically planned before execution even begins. --- ## Project Types – when projects have different natures -Not all projects are the same. -And businesses know this very well. - -Some projects are client implementations. -Others are internal improvements. -Others still involve legal cases, product development, operational support, or research activities. - -The differences go beyond subject matter. -They affect how work is organized, what expectations exist, which stages are involved, how control is applied, and how progress is measured. - -When all these different projects are managed in the same way, familiar problems appear: +Not all projects are the same, and organizations feel that difference daily. +Some projects are client implementations, others are internal improvements, and others involve product development, operational support, advisory work, or research. -- unnecessary fields and steps -- lack of clarity about what really matters -- processes that slow work down instead of supporting it +These differences are not only about subject matter. +They change what information matters, which stages exist, what “done” means, and what controls make sense along the way. +If every project follows the same template, familiar problems appear: irrelevant fields, unclear priorities, and workflows that slow work down instead of supporting it. -That is why in Project Management in @@name, projects are not treated as generic objects. - -They are defined through **Project Types** — the tool that allows each project type to have its own logic, structure, and rules, aligned with how work is actually done. +That is why Project Management in @@name does not treat projects as generic objects. +Projects are defined through **Project Types**, so each type can follow a logic that matches the way the work is actually done. --- ## Project Types – how the system understands what kind of project you are creating -Before a project is created, the system asks a simple but extremely important question: - -**“What type of project is this?”** +Before a project is created, the system asks a simple but important question. +“What type of project is this?” In @@name, this choice is not a formality. -It determines how the project will be structured, managed, and used in real work. - -A Project Type describes the nature of the project — whether it is a client implementation, an internal initiative, product development, a legal case, operational work, or something specific to your business. - -Based on the Project Type, the system knows: - -- what information is relevant for this kind of project -- which Case Categories are allowed -- what working logic should apply +It determines how the project is structured and how it is used in real work. +A Project Type describes the nature of the project, such as client implementation, internal initiative, product development, operational work, or something specific to your business. -This allows projects to adapt to real working practices, instead of people adapting to a universal template. +Based on the selected Project Type, @@name can treat the project differently in practical ways. +It can focus the project on the information that is relevant for that type of work. +It can control which Case Categories are allowed in this kind of project. +It can support a working logic that fits the project, instead of forcing people to adapt to a universal template. --- @@ -67,223 +46,167 @@ This allows projects to adapt to real working practices, instead of people adapt This is where confusion often arises, so the distinction matters. -**Project Type** answers the question: -*“What kind of project is this?”* -It defines the identity of the project and how it works. +Project Type answers the question: +“What kind of project is this?” +It defines the identity of the project and the logic that applies to it. -**Project Group** answers the question: -*“Which projects belong to the same family and should share a common structure?”* +Project Group answers the question: +“Which projects should share the same structure?” It is used when multiple projects need the same Areas and Milestones, without making them global for everyone. -In short: +In short, Project Type defines what the project *is*. +Project Group defines shared structure across multiple projects. -- **Project Type** defines *what the project is* -- **Project Group** defines *shared structure across multiple projects* - -This combination allows project management to be both standardized and flexible. - -**How to choose correctly:** - -- If you want to define the nature of a project → **Project Type** -- If you want multiple projects to share the same structure → **Project Group** +A simple way to choose correctly is this. +If you want to define the nature of a project, use Project Type. +If you want multiple projects to share the same Areas and Milestones, use Project Group. --- ## Case Categories – how project type defines the way work is done -Once a project has its type, the next logical question is: - -**“What kind of work happens inside this project?”** - -This is where **Case Categories** come into play in @@name. - -Case Categories define the types of tasks that can exist within a project and the working logic they carry. +Once a project has its type, the next question follows naturally. +“What kind of work happens inside this project?” -While the Project Type defines *what the project is*, -Case Categories define *what kind of work is performed inside it*. +This is where **Case Categories** come into play in @@name. +Case Categories define the types of work that can exist within a project, and the working logic those tasks carry. +If Project Type defines what the project is, Case Categories define what kind of work is performed inside it. --- ## From structure to real work -In real life, different projects involve different types of activities: +In real life, different projects involve different types of activities. +A team may do analysis, development, coordination, approvals, client communication, support, or internal improvements. +When all of these appear as one undifferentiated list of Cases, it becomes harder to understand what the team is actually doing and what capacity is being consumed by which kind of work. -- analysis -- development -- coordination -- client communication -- approvals -- support -- internal improvements - -Case Categories allow these activities to be clearly distinguished, instead of being mixed into a single list of tasks. - -Each category can have its own logic, such as: - -- different fields -- different statuses -- different tracking approaches -- different working rules - -Tasks are no longer just “another Case”, -but part of a clear working model aligned with the project type. +Case Categories allow these activities to be distinguished in a meaningful way. +Each category can carry its own logic, such as relevant fields, applicable statuses, tracking approach, or working rules. +As a result, tasks are no longer “just another Case”. +They become part of a working model that matches the project type and the team’s real process. --- ## How Project Types and Case Categories work together -This is where the connection to Project Types becomes critical. - -Each Project Type can define: +This is where the connection to Project Types becomes critical. +Each Project Type can define which Case Categories are allowed and which types of work make sense in that project. -- which Case Categories are allowed -- what types of work make sense in this project -- what the expected workflow should be +For example, a client implementation project may allow categories such as Analysis, Configuration, and Testing. +An internal operations project may focus on Requests, Improvements, and Incidents. +A legal or advisory project may include Consultation, Drafting, and Review. -For example: - -- a **Client Implementation** project may include *Analysis, Configuration, Testing* -- an **Internal Operations** project may include *Requests, Improvements, Incidents* -- a **Legal / Advisory** project may include *Consultation, Drafting, Review* - -As a result: - -- teams work with familiar and meaningful categories -- projects have predictable structure -- management gains comparability and clarity +The outcome is practical and reviewable. +Teams work with familiar categories that match their reality. +Projects become easier to understand because work is grouped by meaning, not only by person or date. +Management gains comparability, because projects of the same type follow a consistent classification of work. --- ## Better project management, stronger focus -Case Categories do not complicate work — they **focus it**. +Case Categories do not complicate work. +They focus it. -Instead of all tasks looking the same across all projects: +Instead of all tasks looking the same across all projects, teams can see what kind of work they are doing. +Managers can see which categories consume capacity and where bottlenecks form. +Projects become easier to manage and analyze because work is structured before it becomes overload. -- teams know exactly what kind of work they are doing -- managers see which types of work consume the most capacity -- projects become easier to manage and analyze - -This naturally leads to the next step — -controlling workload and work flow through **WIP limits**. +Once work is classified clearly, the next question becomes unavoidable. +“How much work can we realistically handle at the same time?” +This is where WIP limits create real boundaries that protect flow. --- ## WIP limits – when work flow has real boundaries -Once we define what types of work are being done through Case Categories, the next — and much harder — question appears: - -**“How much work can we realistically handle at the same time?”** - -In many organizations, this question remains unanswered. -The result is familiar: +In many organizations, “work in progress” grows without control. +Too many tasks are started, context switching increases, and progress slows down even when people feel busy. -- too many tasks “in progress” -- constant context switching -- a feeling of being busy, but slow progress - -This is exactly where **WIP limits** come into play in Project Management in @@name. +WIP limits address that problem directly in Project Management in @@name. +They help teams and managers treat work as flow, not as accumulation. --- ## What WIP limits are -WIP (Work In Progress) limits define the maximum number of Cases that can be in a given status or category at the same time. - +WIP (Work In Progress) limits define the maximum number of Cases that can be in a given status or category at the same time. This is not a restriction on people. -It is a restriction on the system — so it reflects the team’s real capacity. - -In simple terms: +It is a restriction on the system, so it reflects real capacity rather than optimistic assumptions. -- when the limit is reached -- new work does not automatically flow in -- existing work must be completed first +In practical terms, when a limit is reached, @@name provides a clear signal. +New work should not flow in automatically. +The best next action is to finish, unblock, or move existing work forward first. --- ## Why this matters for management -WIP limits protect both teams and management from one of the most common traps in project work: - -**assigning more work than can realistically be completed.** - -With WIP limits: +WIP limits protect teams and management from one of the most common traps in project work: assigning more work than can realistically be completed. -- planning becomes realistic -- workload becomes visible -- decisions are based on capacity, not assumptions +With WIP limits, planning becomes more grounded because capacity constraints are explicit. +Workload becomes visible because “in progress” has a measurable boundary. +Decisions can be based on capacity signals, not only on urgency or pressure. -Managers no longer assign work blindly, -but work with a clear signal of when the system is overloaded and when it can take on more. +Instead of pushing more work into the system, managers can see when the system is already saturated. +That makes prioritization more honest and coordination more predictable. --- ## Flow, not a task list -WIP limits change how work is perceived. +WIP limits change how work is perceived. +The focus shifts from how many tasks exist to how tasks move. -The focus shifts: +When teams reduce parallel work, flow tends to improve. +Waiting becomes easier to spot, blocked work becomes harder to ignore, and completion becomes a more consistent outcome. +The goal is not to “do less”. +The goal is to start fewer things at once and finish more reliably. -- from *how many tasks we have* -- to *how tasks move* +--- -Work starts to be seen as a flow, not as accumulation. +## WIP limits as part of the bigger picture -This leads to: +In @@name, WIP limits do not exist in isolation. +They work together with Project Types, which define context, and Case Categories, which define the types of work. +They also work together with User States, which show movement and progress in a way that matches the team’s process. -- shorter lead times -- fewer blocked tasks -- a more sustainable working rhythm +The result is not just stored information. +It is a working system where structure, classification, and capacity constraints support better day-to-day decisions. --- -## WIP limits as part of the bigger picture - -In @@name, WIP limits do not exist in isolation. - -They work together with: +## Why ERP.net -- **Project Types** — defining project context -- **Case Categories** — defining types of work -- **User States** — showing movement and progress +Project Types, Case Categories, and WIP limits in @@name are not “team habits written down”. +They are explicit configuration elements that make the working model visible and shareable. -The system does not merely store a list of tasks. -It actively supports balanced distribution of work. +This improves explainability because the project context, the type of work, and the flow boundaries are recorded in a consistent way. +It improves predictability because workflow and capacity constraints are defined through states, categories, and limits, rather than relying on informal expectations. +And because @@name relies on consistent concepts across the platform, the same classification and flow logic can remain stable as teams grow and projects multiply. --- ## The real value -WIP limits are not a methodology. -They are a **practical decision-making tool**. - -They help: - -- teams work on fewer things, but finish more -- managers plan without overloading people -- businesses achieve predictable outcomes +Project Types, Case Categories, and WIP limits are not a methodology. +They are practical tools for decision-making. +They help teams focus on fewer things at a time and finish more consistently. +They help managers plan without overloading people and without turning status updates into a separate job. Work does not slow down. -It simply starts flowing better. +It simply starts flowing better because the system makes priorities, categories, and capacity constraints visible. --- ## Conclusion -Project Types, Case Categories, and WIP limits work together as a management filter between intention and execution. - -They help businesses: - -- define what type of work is being done -- manage different work streams clearly and predictably -- plan based on real capacity, not urgency or pressure - -The result is not more control, but **better focus**. +Project Types, Case Categories, and WIP limits work together as a management filter between intention and execution. +They help define what kind of work is being done, keep work streams clear and comparable, and plan based on real capacity instead of urgency. Teams understand what they are working on and why. -Management sees where capacity goes and how work moves. - -This transforms Project Management from a tracking tool into a system for better decisions. +Management can see where capacity goes and how work moves. +This turns Project Management in @@name from a tracking tool into a system that supports better decisions. --- From 26af782b33699239c2f4903754cddea157e35cd0 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Sat, 31 Jan 2026 19:20:33 +0200 Subject: [PATCH 28/31] =?UTF-8?q?Rewrite=20=E2=80=9CAssignment=20Rules=20&?= =?UTF-8?q?=20User=20States=E2=80=9D=20subpage=20for=20info.erp.net=20styl?= =?UTF-8?q?e?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Rewrote the sub-article with the same section headings, reducing generic SaaS phrasing and grounding claims in concrete, checkable mechanisms in @@name. Clarified the conceptual distinction between System States (lifecycle phases) and User States (business sub-stages), and explained how they work together. Expanded the “Assignment Rules” section with high-level evaluation logic (trigger on create/attribute change) and deterministic conflict resolution (priority + ordering). Added two micro-scenarios: one illustrating rule-based routing/handovers, and one illustrating how User States make waiting reasons explicit and reportable. Improved readability with sentence-per-line Markdown formatting and clean paragraph breaks. --- .../assignment-rules-user-states.md | 167 +++++++++--------- 1 file changed, 82 insertions(+), 85 deletions(-) diff --git a/features/work-management/project-management/assignment-rules-user-states.md b/features/work-management/project-management/assignment-rules-user-states.md index 4e5cb748..7aec0531 100644 --- a/features/work-management/project-management/assignment-rules-user-states.md +++ b/features/work-management/project-management/assignment-rules-user-states.md @@ -1,118 +1,115 @@ # Assignment Rules & User States ## When project management becomes a process -In @@name, **Assignment Rules** and **User States** transform work management from simple “organization and assignment” into a sustainable, repeatable process: +In @@name, Assignment Rules and User States turn work management from “we organize and assign tasks” into a repeatable process. +Cases reach the right people through explicit routing rules. +Statuses stop being interpretive and become a shared language for teams, managers, and reporting. -- tasks (Cases) reach the right people through clear, predefined rules; -- statuses mean the same thing to everyone — teams, management, and reporting alike. +### Why this matters ---- +Even when projects are well structured and Cases are clearly described, everyday work raises the same operational questions. +Who takes ownership of this Case now. +When is a Case actually ready, and when is it waiting. +What does a status mean in practice, not just in words. +How do we avoid manual assignment and constant clarifications. -## Why this matters +This is the moment where project management moves from a plan to a predictable flow of work. +The goal is not to add bureaucracy. +The goal is to reduce “hidden decisions” and make routing and progress explicit. -Even when projects are well structured and tasks are clearly defined, everyday work inevitably raises questions such as: +### Key capabilities -- Who takes ownership of this task? -- When is a task actually “ready,” and when is it just waiting? -- What does a specific status really mean in practice? -- How do we avoid manual assignment and constant clarifications? +#### 1) Assignment Rules — automated work distribution -This is where project management moves from a plan to a predictable flow of work. +Assignment Rules define how and to whom new or updated Cases are assigned without manual intervention every time. +Instead of relying on a manager’s memory or constant “who takes this” messages, @@name applies rules that the organization has defined upfront. ---- +Rules can be evaluated based on a practical set of Case attributes. +This includes project context (such as project, area, milestone, type, or category) and also progress context (System State and User State). +Rules can also use business context such as the Stakeholder Party, so routing can follow “for whom is this work” and not only “what kind of work is it”. -## Key capabilities +When multiple rules match, @@name resolves the conflict deterministically. +Rules have priority, and when priorities are equal, rule ordering acts as a tie-breaker. +This makes routing stable and explainable, which matters when teams grow and when processes are audited or reviewed later. -### 1) Assignment Rules — automated work distribution +Assignment itself can reflect how the organization operates. +A Case can be routed to a specific person. +It can also be routed to a responsible role or team logic, such as the responsible person for the project or for the project area. +This does not replace management decisions. +It removes repetitive coordination and keeps responsibility visible at the point where work enters the system. -**Assignment Rules** define how and to whom new or updated Cases are assigned — without the need for manual intervention every time. +**Micro-scenario (Assignment Rules).** +A new Case is created in a client implementation project with category “Testing”. +The Case enters a “Ready” System State with a User State like “For review”. +An Assignment Rule routes it to the reviewer role or a specific QA user. +When the User State changes to “Ready for execution”, another rule routes the same Case to the executor role or the delivery team. +The handover is explicit and recorded as part of the Case, rather than happening in chat. -Rules can be based on criteria such as: +Where this delivers the most value is predictable. +It helps larger teams with multiple roles. +It helps repetitive work where routing patterns repeat every day. +It helps request intake and operational flows where new Cases arrive continuously. +It helps service and support models where response time depends on fast routing to the right owner. -- project type -- case category -- project, project area, or project group -- other business-specific conditions +#### 2) User States — a shared language for real progress -The result is consistent routing of work to: +Status words often sound clear until they mean different things to different people. +“In progress” may mean active execution for one person, “we will start soon” for another, and “we are blocked” for a third. +User States solve this by letting the organization define business-meaningful sub-stages that fit the way teams actually work. -- the right team, -- the right role, -- or a specific responsible person. +In @@name, it helps to separate two concepts. +**System States** are the default, predefined lifecycle phases a Case moves through. +They describe the main flow from intake and preparation to execution and completion. +**User States** are custom sub-stages that add granularity inside a System State. +They let teams express what is really happening without inventing new parallel workflows or relying on free-text explanations. -This does not “replace the manager.” -It removes routine work and reduces the risk of missed tasks — especially in environments with a high volume of incoming work. +User States are linked to a specific System State. +They can also be made applicable only for specific Case Categories. +This prevents a “one-size-fits-all” status list and keeps the language relevant to the kind of work being done. +The outcome is simple and practical. +A Case can be in the same System State across the organization, while still carrying the precise business sub-stage that tells the real story. -**Where it delivers the most value:** +**Micro-scenario (User States).** +Two Cases are both in the “Waiting” System State. +One has a User State “Waiting for customer information”. +The other has a User State “Waiting for internal approval”. +Both are “waiting”, but the next action, the expected owner, and the management interpretation are different. +Because the distinction is explicit, reporting and daily coordination stop treating both as the same kind of delay. -- larger teams with multiple roles -- repetitive types of work -- incoming request flows and operational processes -- service and support models +### How it works (high level) ---- +#### Assignment Rules (high level) -### 2) User States — a shared language for real progress +When a Case is created, or when key attributes change, @@name evaluates the active Assignment Rules that match the Case context. +Rules can match on project-related attributes and on progress-related attributes, including System State and User State. +If more than one rule matches, @@name selects the rule deterministically using priority and rule ordering. +The result is predictable routing that does not depend on who happened to notice the Case first. -Statuses often seem clear… until they mean different things to different people. -For example, “In progress” might mean: +#### System States vs User States (high level) -- active work is happening; -- “we’ll start soon”; -- “we’re waiting for information”. +System States provide the main, shared lifecycle of a Case. +User States refine what “work stage” means inside that lifecycle, using the organization’s own language. +Because User States are linked to System States and can be constrained by Case Category, teams can achieve clarity without turning the process into a heavy methodology. -**User States** solve this by enabling: +### Use cases -- clear, business-meaningful status definitions; -- workflows adapted to how the organization actually works; -- elimination of ambiguity around progress. +Assignment Rules and User States are especially valuable for service and support teams, where intake is continuous and fast routing matters. +They help organizations with a steady flow of new Cases, where manual assignment becomes a bottleneck. +They support teams with clearly separated roles, where handovers should be explicit and repeatable. +They help companies that want process without micromanagement, because control comes from shared rules and shared meaning, not from constant manual interventions. -User States are not just labels — they are a shared language between teams and management about what is really happening with a task. +Whether for projects, services, or internal coordination, rules and states reduce dependency on individual people. +They make the process understandable even when priorities shift, teams expand, or new colleagues join. ---- +### Business benefits -## How it works (high level) +By using Assignment Rules and User States, businesses reduce manual coordination and routine task routing. +They shorten the time from “Case created” to “Case owned”, which improves responsiveness in operational work. +They make accountability clearer because responsibility and real work stage are visible on the Case itself. +They reduce operational noise and “bouncing” because handovers are driven by rules and shared status meaning. +They keep the working model predictable as teams grow and change, because the process is defined explicitly, not carried only in people’s habits. -### Assignment Rules (high level) - -- When a Case is created or when key attributes change (e.g. project, category, area), the system evaluates the applicable rules. -- If a match is found, @@name routes the Case to a team, role, or specific owner based on the rule logic. -- Incoming work is distributed predictably, without bottlenecks caused by manual reassignment or clarification. - -### User States (high level) - -- User States define the “intermediate” business stages teams actually use (e.g. *Waiting for info*, *For review*, *Ready*). -- This makes progress measurable and comparable — equally understandable to the people doing the work and those monitoring results. - ---- - -## Use cases - -These tools are especially valuable for: - -- service and support teams -- organizations with a steady inflow of tasks -- teams with clearly separated roles and responsibilities -- companies that want process without micromanagement - *(control through rules, not constant manual assignment)* - -Whether for projects, services, or internal coordination, rules and states provide stability at scale and reduce dependency on individual people. - ---- - -## Business benefits - -By using Assignment Rules and User States, businesses gain: - -- less manual coordination and task routing -- faster response to new tasks (shorter time to ownership) -- clearer accountability — who is doing what, and in which real stage -- reduced operational noise and task “bouncing” -- a predictable way of working as teams grow and change - ---- - -## Continue exploring Project Management +### Continue exploring Project Management **Back to the main topic:** [Project Management in @@name](index.md) From 033b7078441c7f7f09dddc12811aaf09b40568d1 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Sat, 31 Jan 2026 19:36:48 +0200 Subject: [PATCH 29/31] Update assignment-rules-user-states.md lines added --- .../assignment-rules-user-states.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/features/work-management/project-management/assignment-rules-user-states.md b/features/work-management/project-management/assignment-rules-user-states.md index 7aec0531..da7a6b3a 100644 --- a/features/work-management/project-management/assignment-rules-user-states.md +++ b/features/work-management/project-management/assignment-rules-user-states.md @@ -1,6 +1,8 @@ # Assignment Rules & User States ## When project management becomes a process +--- + In @@name, Assignment Rules and User States turn work management from “we organize and assign tasks” into a repeatable process. Cases reach the right people through explicit routing rules. Statuses stop being interpretive and become a shared language for teams, managers, and reporting. @@ -17,6 +19,8 @@ This is the moment where project management moves from a plan to a predictable f The goal is not to add bureaucracy. The goal is to reduce “hidden decisions” and make routing and progress explicit. +--- + ### Key capabilities #### 1) Assignment Rules — automated work distribution @@ -76,6 +80,8 @@ The other has a User State “Waiting for internal approval”. Both are “waiting”, but the next action, the expected owner, and the management interpretation are different. Because the distinction is explicit, reporting and daily coordination stop treating both as the same kind of delay. +--- + ### How it works (high level) #### Assignment Rules (high level) @@ -91,6 +97,8 @@ System States provide the main, shared lifecycle of a Case. User States refine what “work stage” means inside that lifecycle, using the organization’s own language. Because User States are linked to System States and can be constrained by Case Category, teams can achieve clarity without turning the process into a heavy methodology. +--- + ### Use cases Assignment Rules and User States are especially valuable for service and support teams, where intake is continuous and fast routing matters. @@ -101,6 +109,8 @@ They help companies that want process without micromanagement, because control c Whether for projects, services, or internal coordination, rules and states reduce dependency on individual people. They make the process understandable even when priorities shift, teams expand, or new colleagues join. +--- + ### Business benefits By using Assignment Rules and User States, businesses reduce manual coordination and routine task routing. @@ -109,6 +119,8 @@ They make accountability clearer because responsibility and real work stage are They reduce operational noise and “bouncing” because handovers are driven by rules and shared status meaning. They keep the working model predictable as teams grow and change, because the process is defined explicitly, not carried only in people’s habits. +--- + ### Continue exploring Project Management **Back to the main topic:** From abffb1cbb11db7576b5068f9f82dbee918d8f23b Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Sat, 31 Jan 2026 19:38:00 +0200 Subject: [PATCH 30/31] Update assignment-rules-user-states.md lines refinement --- .../project-management/assignment-rules-user-states.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/features/work-management/project-management/assignment-rules-user-states.md b/features/work-management/project-management/assignment-rules-user-states.md index da7a6b3a..71f8073e 100644 --- a/features/work-management/project-management/assignment-rules-user-states.md +++ b/features/work-management/project-management/assignment-rules-user-states.md @@ -1,8 +1,6 @@ # Assignment Rules & User States ## When project management becomes a process ---- - In @@name, Assignment Rules and User States turn work management from “we organize and assign tasks” into a repeatable process. Cases reach the right people through explicit routing rules. Statuses stop being interpretive and become a shared language for teams, managers, and reporting. From 5de5c8b8b0eb6863d51549a4836539d6ba52b561 Mon Sep 17 00:00:00 2001 From: hkostadinov28 Date: Sat, 31 Jan 2026 19:47:34 +0200 Subject: [PATCH 31/31] =?UTF-8?q?Rewrite=20=E2=80=9CAreas,=20Project=20Gro?= =?UTF-8?q?ups,=20and=20Milestones=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Rewrote the sub-article with the same section headings, using sentence-per-line Markdown formatting and clean paragraph breaks. Reduced generic SaaS phrasing by grounding claims in concrete concepts: Project Groups (program-level view), Project Areas (in-project structure), and Milestones (reference points for progress). Added two micro-scenarios to make the concepts practical and verifiable (Project Groups; Areas + Milestones). Clarified the role of program-level financial visibility under Project Groups without overpromising. Included a single screenshot placement recommendation (Project Areas section) to support the core “structure inside the project” message. --- .../areas-project-groups-milestones.md | 155 +++++++++--------- 1 file changed, 73 insertions(+), 82 deletions(-) diff --git a/features/work-management/project-management/areas-project-groups-milestones.md b/features/work-management/project-management/areas-project-groups-milestones.md index f4b34631..42586f87 100644 --- a/features/work-management/project-management/areas-project-groups-milestones.md +++ b/features/work-management/project-management/areas-project-groups-milestones.md @@ -2,135 +2,126 @@ ## When projects start to “think bigger” -In this article, we continue exploring the building blocks of Project Management in @@name — focusing on the tools that help teams and managers understand where work fits, how projects relate to each other, and how progress is measured over time. +In this article, we continue exploring the building blocks of Project Management in @@name. +We focus on the tools that help teams and managers understand where work fits, how projects relate to each other, and how progress is measured over time. -Project Groups, Project Areas, and Milestones are the elements that make this possible. -They give projects shape, logic, and rhythm — without adding unnecessary complexity to everyday work. +Project Groups, Project Areas, and Milestones make this possible. +They add structure above and within projects, and they add clear reference points for progress. +The goal is to help projects scale without turning everyday work into administration. -At the beginning, tasks are enough. - -The team knows what needs to be done, who takes responsibility, and how the work is progressing. - -Over time, however, projects begin to grow. - -More initiatives appear. More people are involved. More parallel activities take place. +At the beginning, tasks are often enough. +The team knows what needs to be done, who owns it, and how the work is progressing. +Over time, projects begin to grow. +More initiatives appear, more people are involved, and more parallel activities take place. Work is no longer just a list of tasks. It becomes a system of connected efforts that need structure, coordination, and a clear sense of scale. -This is the moment when Project Management stops being purely operational — and becomes a management system. +This is where Project Management in @@name benefits from additional building blocks. +They let teams stay operational in their daily work, while management gains a stable way to view progress and priorities across initiatives. +--- ## The structure that makes scale manageable -When projects begin to operate on more than one level, structure is no longer a formality — it becomes a necessity. +When projects begin to operate on more than one level, structure stops being a formality. +It becomes the way teams navigate work without losing context, and the way management sees the full picture without diving into operational detail. -It helps teams navigate their daily work, and it allows management to see the full picture and make more informed decisions. - -In the Project Management module of @@name, this structure is built through three complementary elements that extend the work with Cases and add clarity, scale, and rhythm. +In @@name, this structure is built through three complementary elements. +Project Groups add a level above projects. +Project Areas add logic inside a project. +Milestones add shared reference points in time. +--- ## Project Groups – managing programs of projects -Project Groups allow projects to be combined into logical groupings based on how the business manages them. - -These may be strategic initiatives, client programs, internal transformations, product lines, or any other categorization that makes sense for the organization. +Project Groups allow projects to be combined into logical groupings that match how the business manages them. +A Project Group can represent a strategic initiative, a client program, an internal transformation, a product line, or any grouping that matters to the organization. -At this level, the focus moves away from individual tasks and toward: +At this level, the focus shifts from individual Cases to how projects relate and progress together. +Management can review the overall direction of the program, see where attention is needed, and compare progress across projects that belong to the same initiative. -- the relationships between projects -- the overall progress of the program -- priorities and workload at a higher management level +**Micro-scenario (Project Groups).** +A company runs a client program that includes several implementation projects for different sites. +Each site is a separate project, but all of them belong to one Project Group. +Management can follow progress at program level while teams continue working inside their own projects. -Project Groups form the foundation for **Program Management** — a capability that gives management direction and control, without burdening teams with additional complexity. +--- -### Managing budget at program level +## Managing budget at program level -Project Groups in @@name also allow projects to be managed financially at a higher level. +Project Groups in @@name can also support financial visibility and control at a higher level. +This makes it possible to review planned and actual budgets for the program, track costs across related projects, and adjust allocations when priorities change. -Management can track: - -- planned and actual budgets for the entire program -- costs across multiple related projects -- budget distribution and reallocation when priorities change - -This makes Project Groups especially valuable for organizations managing strategic initiatives, client programs, or long-term investments. +This is especially valuable when organizations manage strategic initiatives, long-term investments, or multi-project client programs. +Instead of reviewing budgets project by project, management can review the initiative as a whole. +--- ## Project Areas – logic inside the project -While Project Groups operate above projects, Project Areas introduce structure within them. - -They allow tasks inside a project to be organized by meaning, phase, or functional logic. - -Project Areas are particularly useful when: - -- a project passes through clearly defined stages -- there are parallel streams of work -- different teams or roles contribute to the same objectives -- task complexity increases over time +While Project Groups operate above projects, Project Areas introduce structure within them. +Project Areas organize Cases by meaning. +They can represent phases, work streams, responsibility domains, or any internal logic that helps the team keep execution clear. -### Phases, streams, and reusable structures +Project Areas are particularly useful when a project passes through defined stages, when there are parallel streams of work, and when different teams contribute to the same outcomes. +They keep the project readable as complexity grows, because the team does not work in one undifferentiated list. -Project Areas can represent phases such as Planning, Execution, Testing, or Go-Live. +--- -They can also reflect functional domains, responsibility areas, or types of work. +## Phases, streams, and reusable structures -A key advantage is that the same Project Area can be reused across multiple projects, creating consistency and enabling cross-project analysis. +Project Areas can represent phases such as Planning, Execution, Testing, or Go‑Live. +They can also reflect functional domains such as Marketing, Communications, Technical Preparation, or Delivery. +The exact structure depends on how the organization works. -This allows management to see how specific phases or workstreams evolve across different initiatives, while teams benefit from clearer structure and focus. +A key advantage is consistency across projects. +When projects share a similar internal structure, teams orient faster and management can compare how similar phases evolve across different initiatives. +The value is not “copying a template”. +The value is having a repeatable structure that supports cross-project understanding. +--- ## Milestones – when progress has clear reference points -Milestones introduce clear reference points in the life of a project. +Milestones introduce clear reference points in the life of a project. +They mark important outcomes, decisions, or delivery moments and answer a simple question. +Where are we right now. -They mark important stages, outcomes, or decisions and help answer a simple but critical question: +Milestones support communication and coordination because they create shared checkpoints. +Teams can plan around them, stakeholders can align expectations, and progress can be discussed without listing every operational task. -**Where are we right now?** - -Milestones: - -- create a sense of progress -- improve communication with stakeholders -- support planning and accountability - -In @@name, Milestones are designed to support orientation and results without introducing unnecessary administrative overhead. - -They provide a shared language between teams and management — progress can be discussed clearly without diving into operational details. +**Micro-scenario (Areas and Milestones).** +An implementation project uses Areas such as Analysis, Configuration, Testing, and Go‑Live. +Milestones mark key moments like Requirements approved, UAT passed, and Go‑Live completed. +The structure stays clear for the team, and progress is easy to communicate outside the team. +--- ## Business benefits – what the business truly gains -The combination of Project Groups, Project Areas, and Milestones transforms project management into a sustainable management approach. - -For the business, this means: +The combination of Project Groups, Project Areas, and Milestones turns project execution into something that scales. +It helps organizations keep clarity when more projects, more people, and more parallel work are involved. -- **Easier management as scale increases** - Projects grow without chaos or constant firefighting. - -- **Clear logic instead of scattered information** - Work is structured by meaning, phase, and responsibility. - -- **Visibility at the right level for everyone** - Teams, project managers, and executives each see what matters to them. - -- **Less operational noise, more autonomy** - Fewer clarification meetings, fewer status questions, more focus on execution. +Management becomes easier as scale increases because related projects can be reviewed together without losing detail where it matters. +Work becomes clearer because Cases are structured by phase and responsibility, not only by date or owner. +Visibility improves because different roles can see the right level of information, from execution detail to program overview. +Operational noise decreases because progress and expectations are anchored in shared structure and milestones, not constant clarification meetings. +--- ## Applicability in real-world work -These tools are particularly valuable for organizations that: - -- manage multiple parallel projects -- run client implementations with defined phases -- coordinate internal programs and transformations -- seek balance between flexibility and management control +These tools are particularly valuable for organizations that manage multiple parallel projects and need a stable way to compare and coordinate them. +They fit well for client implementations with defined phases and deliverables. +They support internal programs and transformations that run over longer periods and involve many stakeholders. +They help teams and management balance flexibility with shared structure and control. -Whether it is a short initiative or a long-term program, the approach remains the same: -**clear structure, shared context, and visible progress.** +Whether the work is a short initiative or a long-term program, the principle remains the same. +Clear structure, shared context, and visible progress. +--- ## Continue exploring Project Management