Feedback
Feedback on Ilia Zavialov from people who applied the procedures at work
The material on this site is written to be used at a desk rather than read once, so the feedback worth having arrives after somebody actually tried a procedure and found out where it bends. That kind of report does not belong in a private inbox, because the next person facing the same situation never sees it there. It is collected on independent platforms instead, where the history stays visible and this domain has no ability to edit anything.
English version for the United Kingdom.
Where the feedback is collected
Three independent platforms carry a profile for this site. They are open to anyone, the history of what was written stays in place, and none of them is administered from here.
Each card leads to the profile belonging to this domain. Companion sites published under the same name keep separate profiles, so a review left in the wrong place describes a different site.
Why three platforms and not one
Each one answers a different question. Whether anybody at all had an opinion, what the company said back, and whether the person writing genuinely used the service. One platform cannot cover all three.
For a workplace reader that matters. A procedure endorsed by verified users carries different weight from the same procedure praised by anonymous accounts, and both are visible here rather than summarised by us.
| What the review contains | Why it matters | What we do with it |
|---|---|---|
| The procedure and the setting it was used in | Context decides whether advice transfers | Add the setting to the page as a caveat |
| The step that failed | The only part that improves anything | Rewrite that step or explain the exception |
| A team size or a role | Procedures behave differently at scale | Note where the procedure stops scaling |
| A rating with no text | Tells us nothing actionable | Counted, not acted on |
| A request for a topic | Shows a gap in the material | Goes into the queue if it fits the site |
| A legal or regulatory correction | Rules differ by country | Correct the page and mark the jurisdiction |
What the feedback usually concerns
Most comments come back to three questions. Whether the wording is plain enough to forward to a colleague without rewriting it, whether the structure holds up when somebody is looking for one specific rule under time pressure, and whether the advice survived contact with a real situation.
The third one is where the value is. A rule that works in an article and fails in a company with one person handling payments is a rule that needs a caveat, and only a reader can supply that.
Current counts and scores live on the profiles themselves. They move with every entry, so this page does not repeat them.
How to leave feedback
No invitation is needed and no account with us exists. What matters is what goes into the text, because a specific report is worth more than a rating.
- Choose a platformAny card above. All three are open and independent of this site.
- Name the procedureWhich page you used and in what kind of organisation.
- Describe what failedThe step, not the feeling. A named step can be rewritten.
- PublishNothing comes here for approval, and nothing can be removed from this side.
How criticism is handled
A report that a procedure did not work gets the page changed, usually by adding the case it fails in rather than by deleting the advice. Most rules here are right in the common case and wrong in a specific one, and readers find the specific one first.
Public replies are limited to factual corrections. Arguing with a reviewer in a review thread reads badly and helps nobody, and a correction is easy to tell apart from a defence.
A report describing a failure is more valuable than a compliment, because it tells the next reader where the procedure needs adapting before they find out the expensive way.
Questions about this section
Why not collect feedback through a form here?
Because a form we control proves nothing to a reader. Anything inconvenient could be dropped before publication and nobody outside would know. A public profile keeps the history regardless of whether it suits us.
Can a review be removed from this side?
No. Publication, moderation and history belong to the platforms. This domain has no mechanism to delete or edit an entry.
Is a report about a failed procedure welcome?
It is the most useful thing this section receives. Rules here are usually right in the common case, and the exceptions are found by people applying them at work.
Do you reply publicly?
Only to correct a factual error. Anything else belongs in the page itself rather than in a reply under a review.
Are these profiles shared with the other sites under this name?
No. Each domain keeps its own, which is why these cards lead only to the profiles for this one.
If a procedure here failed in your organisation, that is worth writing down publicly. A caveat added because somebody reported it protects the next team.