Lodos guides

How teams actually use the thirty modules — what to set up first, what to skip, and where people get stuck.

English Türkçe Deutsch Español Français Italiano

Getting started

• Setting up your first workspace

  A workspace is the boundary every other module reads from. Get the boundary wrong and you spend months moving things.

  6 min read

• Invites, roles, and who sees what

  An invite is cheap. Getting the order wrong is not — half a team that joined before the workspace was ready will quietly stop opening it.

  5 min read

• Which platform for which job

  One account, three shapes. Most people pick one and quietly put up with the parts it is bad at.

  4 min read

• How AI tokens are spent

  There is one balance, not one per module. That is the whole design, and it explains both the good and the annoying parts.

  4 min read

• Bringing work in from other tools

  Most migrations fail in the same place: somebody tries to bring everything, and everything takes longer than anyone allowed for.

  2 min read

• The twenty minutes that protect the account

  Almost no workspace is lost to a clever attack. They are lost to a shared password and a laptop nobody asked about.

  2 min read

• Deciding what is allowed to interrupt you

  Every module ships with notifications turned up, because the people who built it think their part is the important one. All thirty are wrong at once.

  2 min read

• What breaks when the team grows

  Nothing about a small team scales. It just stops working one person at a time, and by the time you notice, the fix is a reorganisation.

  2 min read

• Somebody's first five days

  A new person decides in the first week whether asking questions here is safe. Almost nothing you teach them matters as much as that.

  3 min read

• Templates and work that comes back

  A template is a decision you made once and stopped questioning. That is its value and its entire danger.

  2 min read

• Living inside a plan’s limits

  Nobody reads the limits when they sign up. Everybody meets one eventually, and almost always on the day it is least convenient.

  3 min read

Daily work

• How a piece of work actually moves

  Three modules can hold a to-do. Picking the wrong one is how teams end up maintaining the same list in two places.

  4 min read

• Time tracking that people actually keep up

  Every team that adopts time tracking abandons it around week three. The reason is almost never laziness.

  4 min read

• Which conversation belongs where

  Most teams have one place to talk and use it for everything. That is why nobody can find anything six weeks later.

  4 min read

• Where knowledge actually lives

  Files and notes are the two things nobody sets up deliberately, and the two things that decide whether anyone can find anything in year two.

  4 min read

• Finding the thing you know exists

  You rarely search for something you have never seen. You search for something you remember, and memory does not store keywords.

  2 min read

• Handing work over without dropping it

  A handover fails not because something was hidden, but because the obvious thing was too obvious to write down.

  2 min read

• Twenty minutes on Friday

  A week goes wrong slowly. Nothing dramatic happens; three things quietly stop moving and nobody notices until the deadline does.

  2 min read

• Saying the difficult thing at work

  Most feedback fails before a word is chosen, because it is delivered in the wrong place, months late, wrapped in two compliments.

  2 min read

• Writing to a client without creating a problem

  Clients rarely leave because something went wrong. They leave because they found out late, from the wrong side.

  2 min read

• When a written update beats a meeting

  Half of recurring meetings are a document being read aloud slowly. The other half would be ruined by a document.

  2 min read

• Working on four clients at the same time

  Nobody works on four projects at once. They work on one at a time and pay a toll every time they change which one.

  2 min read

Building

• From a request to documentation somebody reads

  API documentation rots because it is written separately from the requests. Generating it from the collection is the only version that stays true.

  4 min read

• Handing repetitive work to an automation

  The automation that runs every day and saves four minutes beats the clever one that runs monthly. Start smaller than feels worthwhile.

  4 min read

• Testing on devices you do not own

  A simulator tells you about layout. It cannot tell you how the page feels on a four-year-old Android, and pretending otherwise is how bugs reach production.

  4 min read

• Shipping a change without a bad evening

  The question before any release is not whether it works. It is what you will do in the twenty minutes after it does not.

  3 min read

• Before you act on a number

  A number in a report has authority it did not earn. Four questions give it back the humility it should have arrived with.

  2 min read

• Deciding whether to automate it at all

  The question is not whether a task could be automated. Almost anything could. The question is whether the automation will still be right in six months.

  3 min read

• The first thirty minutes of something breaking

  The instinct when something breaks is to find out why. That is the second job. The first is to stop it costing anything.

  2 min read

• Depending on somebody else’s service

  Every external service you connect is a part of your product you do not control and cannot fix. That is fine — as long as you decided it deliberately.

  3 min read

• Taking over something somebody else built

  Every inherited system looks worse than it is, for the same reason every unfamiliar city looks badly planned.

  3 min read

• A backup you have never restored

  Everyone has backups. Far fewer have restores, and you find out which kind you have on the worst day of the year.

  3 min read

Modules · AI

• Asking your database a question

  The quality of the answer depends far more on what you point it at than on how you phrase the question.

  3 min read

• Auditing a site you inherited

  An audit that returns forty findings is not a to-do list. Three of them matter and the rest are noise until those three are done.

  2 min read

• Scanning a file you were sent

  The useful question is not “is this a virus” but “was I expecting this file”. The scan supports that judgement, it does not replace it.

  2 min read

• Virtual try-on that produces a usable image

  The output is only as good as the input photo. Almost every disappointing result traces back to the picture, not the model.

  2 min read

• Producing a short video without a crew

  The storyboard is not a formality. Skipping it is the single most expensive habit in this module.

  2 min read

• Generating a site, then making it yours

  Generation gets you to a draft in a minute. The hour after that is what decides whether it looks like yours or like everyone else’s.

  2 min read

Modules · Developer

• When a request fails and you do not know why

  Most “the API is broken” reports are a request that never said who it was. The response usually says so, in the part nobody reads.

  2 min read

• Writing the part the generator cannot

  Generated docs answer “what does this endpoint take”. Nobody was ever blocked by that question.

  2 min read

• Using the DevTools inside the panel

  The multi-device preview gets the attention. The DevTools underneath it are the reason you stop switching to a browser.

  2 min read

• Why there is a browser inside a workspace

  It is not trying to replace Chrome. It exists so that a link you find at 11am is still findable at 4pm.

  2 min read

• Reading and building a node graph

  A flow you can read six months later is worth more than a clever one. Layout is not decoration here.

  2 min read

• Diagrams that survive the meeting

  Most diagrams are drawn once, admired for a week and then quietly become wrong. The ones that last were drawn at the right level.

  2 min read

• A code editor for the edit you make once

  It is not trying to replace your IDE. It replaces the ten minutes of setup before a five-minute change.

  2 min read

• The utilities you stop pasting into random sites

  You paste a payload into an online JSON formatter without thinking. That payload sometimes has a customer in it.

  2 min read

• 3D when you need a shape, not a model

  It is for the moment when a drawing cannot answer the question and a full 3D pipeline is absurd.

  2 min read

Modules · Collaboration

• Running a community, not just a team chat

  Team chat and community are different jobs. The second one has an audience, and an audience behaves nothing like a team.

  2 min read

• Running the call itself

  Half of what makes a call work happens before anyone speaks, and most of it is about the link.

  3 min read

• The day of the event

  Nearly every event problem is a door problem, and the door is decided weeks earlier.

  3 min read

• Letting people in, and out

  Adding someone takes ten seconds. Removing them takes remembering, which is why nobody does it.

  2 min read

• Mail that stays next to the work

  The point of mail inside a workspace is not to replace your mail client. It is to stop the copy-pasting.

  2 min read

Modules · Productivity

• When the board stops telling the truth

  A board is only useful while it matches what is actually happening. Most stop doing that within a month.

  2 min read

• What the hours are actually for

  Tracked time answers one question well: what does this kind of work really cost us? Everything else is a side effect.

  2 min read

• Checklists people actually read

  A checklist is not a list of things to do. It is a list of things that get forgotten.

  2 min read

• Notes you can find again

  Writing a note takes a minute. Finding it eight weeks later is the part nobody plans for.

  2 min read

• A calendar that reflects your actual week

  If your calendar only contains meetings, it says every other hour is free. None of them are.

  2 min read

• Files a stranger could navigate

  The test of a drive is not whether you can find things. It is whether someone who joined last week can.

  2 min read

• How many workspaces you actually need

  Most teams need one workspace and think they need six. The extras do not organise the work — they hide it.

  2 min read

• A pipeline that tells you something

  Most CRMs die of two things: stages nobody can define and fields nobody fills. Both are fixable in an afternoon.

  2 min read

Modules · Downtime

• Music that helps you work

  Music is not background. It competes for the same attention the work needs, and what you choose decides who wins.

  2 min read

• Breaks that actually restore you

  Not all breaks rest you. Some just move the tiredness somewhere else and hand back a worse afternoon.

  2 min read