Find published personal stories and reporting about recovery, setbacks, and starting again. Otentick writes a short guide to each source and links you to the original publisher, where you can read the full story.
These are independently published stories, not Otentick member submissions. We credit the source and author where available; inclusion does not imply endorsement by the author or publisher.
Natagon built a software product to solve a problem in his own agency and made it profitable, but eventually chose to close it because the work no longer held his interest. The story raises questions about sustainability, motivation, and what success means beyond revenue.
Sean writes about the difficulty of telling his partner and family that gambling had become a problem. Their response was more supportive than he expected, and his story focuses on honesty, rebuilding trust, and asking people close to you for help.
After work stress contributed to anxiety and depression, Bethany left her job and withdrew from daily life. Learning a new skill and building a small business gave her more control over her schedule, while she also learned to ask for support and pace herself.
Aazar Shad recounts an attempt to connect travelers with people who needed unusual items transported. The idea addressed a real personal inconvenience, but trust, marketing, and team fit made it hard to turn into a functioning service.
Will Sun and his co-founder tested a medication-adherence app through a pilot, then found that users did not keep engaging as they had hoped. Their account shows why retention and observed behavior matter beyond positive feedback about an idea.
Kirsty describes how anxiety affected her confidence at work and how a supportive conversation with a manager led to practical adjustments. Her experience highlights how listening and flexibility can make a difference in the workplace.
Alan Murray built an online service intended to make buying a home easier, but low engagement showed that the first version was not solving a strong enough need. He shares how facing that evidence helped him decide to stop.
Andy Goldschmidt reflects on ABBY, a service for documenting A/B tests. The product faced the challenge of teaching users why the category mattered, illustrating how education and adoption can be as difficult as building the software.
Hampus Jakobsson describes how Brisk’s sales software became too broad and too dependent on Salesforce. The experience led him to a useful product lesson: choose a focused customer and solve one important problem well.
Kevin Lamping made a breathing and observation app, then struggled to give it enough sustained attention alongside work and family commitments. His reflection is about the limits of time and the value of building an audience while testing a side project.
Pat Walls reflects on Delite, a business-to-business wholesale ordering product that did not address a pressing enough customer need. He discusses the importance of building around a problem he cares about and testing a small idea in the real world.
Kirill Vechtomov discusses a human-resources product that tried to address workplace communication with software. The experience taught him to distinguish problems technology can solve from problems that require changes in human behavior.