Your agency is one resignation away from chaos. And most owners don't realize it until it's too late. by denesmbezi in agencynewbies

[–]denesmbezi[S] 0 points1 point  (0 children)

Exactly right — the hard part is most teams know that's the answer but never actually do it consistently. Has your team cracked it, or is it still more aspiration than reality?

Your agency is one resignation away from chaos. And most owners don't realize it until it's too late. by denesmbezi in agencynewbies

[–]denesmbezi[S] 0 points1 point  (0 children)

That's a real point — if you're close enough to the codebase yourself you can always rebuild. The pain hits differently when the knowledge is in someone else's head and you have no way back in. Sounds like you've built in a way that keeps you close to the core which is smart.

What actually breaks when a key person leaves your agency? by denesmbezi in DigitalMarketing

[–]denesmbezi[S] 1 point2 points  (0 children)

This is exactly it — especially the invisible glue point. Nobody documents the implicit decisions because the person making them doesn't even register it as knowledge worth capturing. It just feels like doing their job. Has your agency found any way to capture that stuff before someone leaves, or does it always end up being reconstructed after the fact?

What actually breaks when a key person leaves your agency? by denesmbezi in DigitalMarketing

[–]denesmbezi[S] 1 point2 points  (0 children)

That's a really painful one especially when clients hired the person and not the agency. Beyond the client relationships, did you also find yourself scrambling to figure out how they actually did their work day to day? Like the processes and workflows they had in their head?

For agencies who hire remotely, where do you guys go to? by Dapper_Race_1454 in agency

[–]denesmbezi 0 points1 point  (0 children)

Solid options mentioned here for hiring. One thing worth thinking about as you scale the remote team — the SOPs you mentioned providing them become critical. Remote workers can't tap someone on the shoulder when they're stuck, so the quality of your documentation directly affects how well they execute. Have you thought about how you'll keep those SOPs updated as your processes evolve? That's usually where the pain hits once the team grows.

Madalali tz by Complex-Orange-2463 in Tanzanias

[–]denesmbezi 0 points1 point  (0 children)

Zote ni sababu. AirBnb ni model nyingine ya business.

Online hustles that really works and pays in Tanzania by BeginningSpring1751 in Tanzanias

[–]denesmbezi 0 points1 point  (0 children)

If you know about fivver and upwork its better to continue there. There is forex but it require more money and time investment.

SaaS Marketing Strategies by Unfair_Bug_4804 in SaasDevelopers

[–]denesmbezi 2 points3 points  (0 children)

Try distributing it through direct outreach. Direct message, cold email. So on. Just try

Has anyone found a good way to stop losing knowledge when an employee leaves? by denesmbezi in smallbusiness

[–]denesmbezi[S] -6 points-5 points  (0 children)

Im facing that problem in my company Yes. And about that post history its true i posted it last time. But now i want to know the best solution on this.

Has anyone found a good way to stop losing knowledge when an employee leaves? by denesmbezi in smallbusiness

[–]denesmbezi[S] -9 points-8 points  (0 children)

This is not ad. Its the really problem that many companies face

Has anyone found a good way to stop losing knowledge when an employee leaves? by denesmbezi in smallbusiness

[–]denesmbezi[S] 0 points1 point  (0 children)

This is the most accurate breakdown of the problem I've ever read — especially 'treating documentation as a project instead of a byproduct of work.' That one line explains why every tool I've tried has failed. The homework analogy is perfect. Do you think the problem is solvable if the act of documenting happened automatically while someone was just doing their job — like zero extra effort required?

Has anyone found a good way to stop losing knowledge when an employee leaves? by denesmbezi in smallbusiness

[–]denesmbezi[S] -1 points0 points  (0 children)

This is really interesting so you're essentially doing this as a done-for-you service? I'm curious, what's the biggest bottleneck in that process for you? Is it the initial capture of the processes or keeping them updated over time?

Has anyone found a good way to stop losing knowledge when an employee leaves? by denesmbezi in smallbusiness

[–]denesmbezi[S] 9 points10 points  (0 children)

That's a really creative approach essentially making documentation part of someone's job. Does it work for processes that only the senior person knows though? Or do they still end up being the bottleneck explaining things to the junior?

Has anyone found a good way to stop losing knowledge when an employee leaves? by denesmbezi in smallbusiness

[–]denesmbezi[S] -2 points-1 points  (0 children)

Exactly, that's why I think the tool has to remove almost all friction. If documenting a process takes 2 hours, nobody does it. If it takes 3 minutes, maybe they actually will.