Nabil Samari logoNabil Samari logo
  • Home
  • About
  • Blog
  • Portfolio
  • Contact
FI|EN

Popular tags:

AIEvents
Sign in
Nabil Samari logoNabil Samari logo
  • Home
  • About
  • Blog
  • Portfolio
  • Contact
Copyright 2026 © Nabil Samari
  • Home
  • Blog
  • AI Won't Fix the Wrong Priority

AI Won't Fix the Wrong Priority

Nabil Samari
Nabil Samari
July 22, 20268 min read
Share
AI Won't Fix the Wrong Priority

AI can help you do more, but it can also just make the wrong work faster. It won't decide for me whether the whole thing is worth doing in the first place.

Sometimes the best way to get more done isn't a new automation. It's the decision to stop doing the wrong thing entirely.

I've spent the last few years going deep into AI, automation, and technology. I've built websites, applications, AI agents, automated workflows, and entire systems on my own machines. I can code and I can usually build a solution to almost any practical problem.

That's also where the danger lies. When you can automate almost anything, you easily start imagining that almost everything is worth automating.

AI can help you do more, but it can also just make the wrong work faster. It won't decide for me whether the whole thing is worth doing in the first place.

This is probably the most important lesson I've learned from using AI: a good decision is often more powerful than good automation.

Technical Skill Wasn't My Problem

For a long time I thought the next level would come from a better system. Too many tasks? Build an automation. Projects spiraling out of control? Build a dashboard. Communication taking too long? Build an agent.

And honestly, many of those solutions have been genuinely useful. AI helps me with writing, sales preparation, research, reporting, and routines. I've been able to do things alone that would have required a small team just a few years ago.

At the same time, I noticed I was also doing more efficiently the things that weren't taking me anywhere.

So my problem wasn't always a lack of capacity. I was spending my capacity in too many directions. No new tool, better prompt, or one more automation fixes that. Only prioritization does.

Canceling Pälkäne Summer Days Was a Hard but Important Decision

Pälkäne Summer Days is the most concrete example.

The event was far along. The venue was secured. A broad artist lineup had been arranged for two days, along with a host and other programming. Ticketing, the website, marketing, partnerships, and practical production had all progressed. It wasn't just an idea on paper — it was a real event that a lot of work had gone into.

And it could have gone just fine.

Nabil Samari

An events, sales and marketing professional building digital services and local AI solutions.

Location

Helsinki
Finland

Tags

      Newsletter

      Subscribe to receive the latest articles directly by email.

      © 2026 Nabil Samari

      Instagram
      LinkedIn
      YouTube

      That's exactly why canceling it was so hard. It's easy to kill a project that isn't moving forward or one you no longer believe in. Much harder is saying no to a project that's interesting, fun, and potentially successful.

      When I looked at the whole picture honestly, whether I could do it was no longer the right question. The right question was whether the event had a sufficiently sustainable financial and production foundation — and whether it made sense for me to tie up such a large portion of my time, energy, and financial risk in it. The answer was ultimately no.

      The decision was sealed by a very personal observation: I noticed I was starting to forget things I normally wouldn't forget. A few mishaps happened along the way, and I realized I was spinning at so many RPMs that the situation was no longer sensible. That was the moment I thought: something has to give now. Just making things more efficient wasn't enough anymore. The load genuinely had to come down.

      Even a small festival requires production, personnel, permits, safety, marketing, infrastructure, and a massive amount of coordination. A large share of the responsibility was practically on me. Even if I had automated communication, social media, task lists, and tracking as far as they'd go, that wouldn't have removed the event's financial risk or the fact that my attention would have been locked on one heavy project for months.

      Canceling didn't mean the event couldn't have turned out great. It meant that possible success alone wasn't enough justification to continue.

      I decided to focus my energy on things that support me better over the long term: day job, sales, developing my technical skills, more sustainable projects, and building the next phase of my career. At the same time, I decided to reduce the projects where I am the entire engine.

      In hindsight, canceling the event was a bigger productivity decision than any automation I could have built around it.

      It freed up time on the calendar. But even more, it freed up space in my head.

      I've Been Learning to Say No to Good Things Too

      Prioritization easily sounds like cutting out the unpleasant and bad things. In reality, the hardest part is cutting good things.

      You don't have to say yes to every fun thing. You don't have to execute every interesting project. Not every opportunity is my opportunity, even if I could do it and even if it could turn out well.

      This has been a big shift for me. I'm a builder by nature. I get excited about a new idea easily and quickly see how it could be done. Technical skill reinforces this, because the barrier to starting a new project is low. I can build a site, a system, or an automation fast and make an idea look real before I've even decided whether it belongs in my life.

      That's why I've adopted a simpler rule: one real top priority at a time. Other ideas can wait. If something new comes in, something old has to go out.

      This doesn't feel as efficient as building a new system. But in practice, it works better.

      A Full Calendar Doesn't Automatically Mean Good Business

      The same thinking has changed how I approach DJ gigs.

      I used to think a packed calendar was a sign things were going well. When weekends are full of gigs, it looks like demand is there and things are moving.

      I've been DJing for a long time. I'm not just selling a few hours of music — I'm selling years of experience, the ability to read a crowd, reliability, preparation, and the fact that the night works without unnecessary hassle. A gig's real cost also isn't just the time spent on stage. It includes preparation, travel, the late night, and often a chunk of the next day's energy.

      When you add all that up, there's no point competing at the market's cheapest end or taking every offered gig just to have an entry in the calendar.

      I raised my prices for weddings and other private gigs by about 40 percent. Not because I just want to charge more, but because I believe people value quality over the lowest possible price for their important days. Weddings and other one-off celebrations aren't situations where most people want to risk saving in the wrong place. When the moment really matters, you want a skilled and reliable professional there.

      I've also been learning to accept that not everyone will buy after the increase. That's part of it. The goal isn't to get every gig — it's to get the right gigs at the right price.

      If some weekends stay free in a given month, I no longer automatically think I've lost something. A free weekend means rest, better recovery, and more energy for the day job. That can improve next week's sales, decision-making, and overall daily quality more than one poorly priced gig would improve the bank balance.

      Not everything needs to be turned into money right away. Rest has value too.

      AI Is a Lever, Not a Compass

      I haven't turned against AI. Quite the opposite. I use it daily and I believe its significance at work will keep growing.

      But I've changed the order.

      First I decide what matters. Then I figure out what's actually blocking progress. Only after that do I ask whether AI or automation can help.

      If the bottleneck is a bad offer, you need a better offer. If the problem is a price that's too low, you need the courage to reprice. If the calendar is full of the wrong work, you don't need a more efficient calendar. You need the word no.

      AI works best when the direction is already chosen. It can speed up research, prepare options, handle repetition, and free up time for work where human judgment, experience, and responsibility are what make the difference.

      But it doesn't get to choose the direction just because it makes doing more of everything possible.

      I Don't Want to Use AI to Cram More Doing Into My Life

      I'm still technical, curious, and excited by new possibilities. I'll definitely keep building new systems and automations. The difference is that I no longer treat volume of activity as the most important metric.

      I want to do fewer things, but ones that genuinely produce results, grow my skills, or move my life in the direction I want.

      I don't want to use AI to constantly cram more doing into my life. I want to use it so that important things get more time.

      Sometimes that means building a new tool. Sometimes raising a price or leaving a weekend empty. And sometimes it means canceling an entire festival, even if it could have turned out great.

      AI can help me execute my decisions faster. But it won't fix the wrong priority. That responsibility still falls to me.

      #AI#Prioritization#Entrepreneurship#Events#Work Life

      Subscribe to newsletter

      Get the latest posts straight to your inbox.

      No spam. Unsubscribe anytime.

      Latest
      I Built an AI Lead Pipeline That Isn't Allowed to Send Anything
      I Built an AI Lead Pipeline That Isn't Allowed to Send Anything
      August 10, 2026
      OpenAI Wants to Become Part of Everyday Life. Here Is How I Route My AI Work
      OpenAI Wants to Become Part of Everyday Life. Here Is How I Route My AI Work
      July 31, 2026
      I Tested Five Local Coding Models — Not One Built a Working App on the First Try
      I Tested Five Local Coding Models — Not One Built a Working App on the First Try
      July 29, 2026
      I Built a Local RAG Search. Having the Right File Wasn't Enough
      I Built a Local RAG Search. Having the Right File Wasn't Enough
      July 29, 2026
      Popular tags
      AIYrittäjyysHenkilökohtainenKoodausTapahtumatTekoälyTeknologiayrittajyysTutorialGuideTechnicalADHDProjektiTyönhakuFestivaalitPälkäneen KesäpäivätValokuvausYökerhotKalustoVinkitLuova alaLuovuusSEO
      Subscribe

      Get new posts straight to your inbox.