Getting Started

Getting started with LadVen OS should be built around the first manageable process, not around isolated buttons. The goal of the first day is to confirm that the team understands roles, can create a task with an expected result, sees notifications, and can complete work without side agreements.

LadVen OS is an operating system for business. The first route shows not only task creation, but also the management loop: who sets the expectation, who owns the result, where files live, how questions are recorded, and how a manager sees work moving.

Where to Start in Your Role

• Business owner. Your goal is not to learn every section, but to gain transparency: where the work is, who owns it, and what is at risk. Complete the first route below, then read the owner signals and choose a familiar case in the business scenarios.
• Department manager. You will live in slices and acceptance. After the first route, set up task list views for your department and establish a weekly control rhythm.
• Employee. Your loop is the tasks where you are assignee or co-executor: result, deadline, checklist, files, and comments. The first route and the Tasks section are enough to begin.

Before the First Run

• choose the interface language for the team;
• check names, avatars, and participant roles;
• agree which real process you will use for the first test;
• prepare 1-2 files or links that are usually attached to this work;
• decide who will be requester, assignee, co-executor, and observer.

First route

1. Sign in to LadVen OS and check the profile: name, avatar, interface language.
2. Open tasks and create an example of a real process, not an empty test task.
3. Describe the result: what must be ready, in which format, and by what deadline.
4. Assign participants by role: requester, assignee, co-executors, observers.
5. Add a checklist if the result consists of several steps.
6. Attach a useful file or link so the assignee does not search for materials separately.
7. Write a comment with a question or clarification and check who receives a notification.
8. Update status, record progress, and complete the task through result acceptance.

Rollout: the First Two Weeks

Do not try to turn everything on at once. The working sequence goes from people to processes:

Step	What to do	Where it is described
1. People and structure	Add employees, departments, and roles. Check that managers can see their teams.	Company and teams
2. First process	Run one real process through a task with acceptance, using the first route above.	Tasks
3. Team rules	Agree on three rules: a decision without a task does not exist, each task has one owner, and decisions are recorded in task cards.	Meeting to tasks
4. Manager slices	Set up slices for overdue tasks, tasks without an assignee, and tasks waiting for review, then choose a weekly review day.	Weekly rhythm
5. Clients	Move active clients and current deals into CRM. Do not migrate the archive first; start with live work.	CRM
6. Repeatable work	Turn the first repeated task into a template and the first regular task into a schedule.	Templates and automation

By the end of the second week, the team should have a working loop: tasks with acceptance, control slices, live clients in CRM, and the first standard. Add rule and process automation only after the manual loop is stable, following the delegation ladder.

What a Manager Should See

After the first route, a manager should understand:

• where responsibility for the result is visible;
• how a task shows deadline, priority, files, checklist, and comments;
• where notifications appear and which ones require action;
• how to review change history and execution progress;
• what should later be standardized through templates or recurring tasks.

A Good First Task

Choose a scenario the team really performs: preparing a report, checking a contract, approving materials, handing a result to a client, or launching a recurring process. Do not start with an artificial task that has no meaning; it will not show how LadVen OS helps manage work.

Common Mistakes in the First Two Weeks

• Turning everything on at once. The team drowns in sections and returns to messengers. Follow the table above: one process, one habit.
• Test tasks "for the sake of testing". A task named "check the system" proves nothing. The first task should be real work with a real result.
• Half the work in the portal, half in chats. As long as decisions live in two places, there is no transparency. Introduce the rule "a decision without a task does not exist" on day one.
• No acceptance. Assignees close tasks without review, and the manager loses the control point. Agree that closing goes through the requester; see Closing a task.
• Migrating the entire CRM archive. Old deals consume weeks of migration time. Start with active clients; the archive can come later.
• Expecting the system to create order by itself. LadVen OS makes work visible, but the manager sets the rules: roles, control rhythm, and standards.

If Something Works Differently Than Expected

Record where the issue appeared: section, action, user role, and expected behavior. If the process lacked a field, notification, access right, template, or report, treat it as a process setup question, not as a reason to return to spreadsheets. How to pass a question to the LadVen OS team is described in Testing.

Next Step

• Tasks — setup, participants, checklists, files, control, and closing.
• Weekly manager rhythm — how to control work without manually collecting statuses.
• Business scenarios — ready-made routes for familiar management situations.