Category: Podcast

In this episode Ralph Quintero and I break down the process of systemizing your business, and share a standard operating procedure template that you can use to systemize your business.

Systemize Your Business With This Standard Operating Procedure Template – Episode Highlights:

1. How to break down complex procedures into documented systems that you can hand over and delegate.
2. An SOP template that you can use to start systemizing your business – today!
3. Online tools you can use to both document your business, and manage your projects.
4. Recommended books and resources about systemization and standard operating procedures.
5. A free Standard Operating Procedure template for you to use to start systemizing your own business!

We Want To Help You!

My cohost on today’s show, Ralph Quintero, has helped some of the world’s biggest brands improve their systems and become more scalable, efficient, and successful.

Today, Ralph and I want to offer our help to the listeners of the Inspiring Innovation podcast:

We would like to help you take the first step toward systemizing your entrepreneurial business. It will be 100% free of charge, and it is our gift to you for listening to the show (as well as a great way to celebrate the show reaching episode 80!)

All you have to do in order for us to help you take your business to the next step is this:

1. Share this post on your favorite social media
2. Leave a comment below saying what excites you the most about systemizing your business
3. Email me at [email protected] and tell me: What is the most complicated, most time-consuming, or most annoying task that you have? What task would love to systemize and get off of your shoulders? (Even if you don’t believe it’s possible!)

We will choose a listener from the emails and help him – live on the show – to kickstart his systemization project (or take it one step further, if the project already started!)

Benefits Of Standard Operating Procedures

By having SOP’s in place, you drastically improve the agility of your business; New employees can get started immediately, with very little training – if any. You can hire less qualified personnel (equals: less expensive, and easier to find), while maintaining a consistent level of quality in your tasks.

Even if you are the only employee in the business, having an SOP in place will free your mind from remembering technical details, and free you to spend more effort and thought on the business rather than in the business.

An extra benefit for the entrepreneurs amongst you, is that SOP’s are easy to be copied between different businesses and ventures, so the return on the work you will put in when writing them once will be far greater.

What Processes Can Be Systemized Into Standard Operating Procedures?

Considering the fact that everything that happens in McDonald’s is a result of the system – from offering you an apple pie while you order, to how the tomatoes and lettuce are organized inside the bun – almost anything can be systemized.

When it comes to entrepreneurship and online businesses, you will commonly be looking at things such as:

• Social media tasks (sharing stuff on social media, handling inbound social media, handling outbound social media, etc.)
• Handling incoming calls, emails, and inquiries
• Finding and researching potential leads, customers, podcast interviewees, JV opportunities, etc.
• Streamlining webinars – from taking care of the technical part and the set up, and all the way to scripting it and having someone else run the entire show
• Handling service/support calls & emails
• Creating and reproducing content
• Creating graphics and other creative
• Search engine optimization and planning
• Technical management; buying domains, setting up WordPress sites, uploading files, updating plug-ins, managing settings, etc.
• And much, much more

What about more complicated processes?

As Ralph Quintero explained in today’s episode, some processes require “exploratory procedures”. Unpredictable by nature, they are quite hard to break down to a yes-no algorithm. So what can you do about it?

First, you reduce the “before” and “after” around those exploratory procedures to the minimum by systemizing as much as possible of what needs to happen around those procedures. Remember, an 85% systemized and documented procedure is far better than 0%! 

Another way to look at it, was suggested by James Schramko on a previous episode: Many times when something can’t be systemized, he noted, it is because the input going into the process is unpredictable and inconsistent. In such cases, putting a system in place that will make the input more structured, consistent, and predictable will often allow to get rid of the “exploratory procedure” and create a seamless process.

An example for this is podcast editing. I previously was unable to systematize the post-production of my podcast. Editing the show required making decisions of what to cut and what to leave in, decisions that only I could make. This meant that only I could edit my own show, which was (of course) a terrible waste of time.

James suggested that the problem does not truly rely in the complexity of editing, but rather in the inconsistent structure of my raw recordings. By applying a new planning & outlining procedure into my podcasting process, and defining an episode structure –  episodes became predictable and consistent, and editing them finally became delegation-able!

Ask yourself: what complicated process am I struggling with, that would have been a lot easier if what comes into that process was more consistent? Then put a system in place for that input, before trying to systemize the exploratory procedure!

How To Create Standard Operating Procedures (SOP) That Work?

An operating procedure’s quality is measured by:

• How detailed it is – is all the information that’s required to complete the task included in each step?
• Simplicity – is the standard operating procedure written in a clear, understandable, step-by-step manner?
• Actionable – are the actions required clear? Could a 15 years old read and act upon the steps?
• Measurable – are the expected results/deliverables of the procedure clear?

Other factors determining the success of the SOP include:

Relevance – is the SOP up to date? Standard operating procedures should be living documents, not carved in stone. This is much easier to achieve in this day and age with the many online tools available at our disposal, some of which are reviewed at the end of this post.

Usability – is the SOP formatted in a way helpful to completing the tasks?
For instance, for a technical procedure that is to be completed inside a specific piece of software; does the SOP includes screenshots that help the assignee follow the steps? If appropriate, is the SOP in video or audio format? Is it formatted in a way that’s easy to follow when actually conducting the task?

My Standard Operating Procedure Template

I try to create an SOP for every task that repeats itself in my business more than once.

The format below encapsulates everything that needs to be known about a task, in order to complete it successfully. It is a combination of what has been working in my business and what has been working in Ralph’s businesses.

You can download it as a printable PDF/editable Word document here: Download The Standard Operating Procedure Template [It’s FREE!](Remember to adjust the template to fit the needs of you, and your business.)

Task title

Each task has a short title encapsulating what the task is about. Note: Keep it short. The title doesn’t need to encapsulate the “how” or the “why”.

To clarify this, I’ll give you an example: Let’s say that I have a task of defining the title, description, subtitle, and release date of a podcast episode. In Inspiring Innovation, we call this “defining the episode’s metadata”… So this task will be titled “Episode Metadata”, not “define title and description for episode”!

Similarly, the task of taking the show notes I wrote and creating a WordPress post out of them isn’t titled “copy show notes from Google Drive and paste them in WordPress in a new post and stylize it”, but rather “Create WordPress post”.

Task owner

For every task, even before it is assigned, is is known and defined in advance what type of employee will run the task. This is defined by the task owner, and examples are: project manager, audio editor, transcriber, graphic editor, admin, etc.

This allows any manager (in my case, Julie or me) to assign a task when it is to be completed to an appropriate employee, without reading through the entire workflow and figuring out time and time again, “who’s this for? who can do this?”

It also allows everyone on our virtual team to search for open and unassigned tasks relevant to their role, assign it to themselves and get going automatically, instead of us needing to manage those assignments manually.

I mentioned on some previous episodes that we are using Asana to manage our systems and projects. Since Asana doesn’t have a “task owner” field (only an “assignee” – which is a specific person, not a role) I thought I’d mention how we handle this field:

We achieve this by adding tags to the task. For instance, we would add the tag #transcriber to mark the task as owned by the transcriber role. We begin owner tags with a ‘#’ to differentiate the tag from other tags (such as @pendingApproval, using the @ to mark a ‘task status’ tag).

Task Timing

Every task needs to take place in a specific timing – activated either by a specific trigger, or by a predefined frequency.

For instance, the “Create WordPress post” task I mentioned earlier, is triggered by the completion of the “write show notes” task. But our task for blocking IP addresses of people that are trying to hack into our systems, titled “Block Offending IP’s”, is a task that takes place every morning, or in other words – is activated by frequency, in this case “daily” – without any other external trigger.

Task assignee

Since we use Asana, our SOP’s and tasks live in the same place, together. The SOP is saved in a template project, that we duplicate upon need. For instance, as I shared in this post, all the tasks for creating a podcast episode from start to finish exist in a template project that we duplicate every week for that week’s episode.

So our SOP’s become the actual tasks that are assigned to people on my team to work on. Meaning, it’s not a separate operational manual, but actually becomes a living task. This adds another field to my SOP, that wasn’t relevant when operating procedures were kept separately from task management systems: the assignee.

The assignee is the specific person, not role, who is in charge of completing this instance of this task (even if some steps of this task are to be completed by someone other than the assignee, the assignee holds full responsibility for the successful and timely completion of the task).

Task due date

Just like with “task assignee”, since all our SOP’s become tasks in Asana, every task has a due date. This is, of course, the last possible/acceptable date by which this task is to be completed.

The assignees are empowered to complete their tasks as early as possible, obviously!

Task notes

The task notes are used to quickly describe the context of the task; what is this about? what is this for? For example:

“This task is about creating a shareable image that we can post on our social media accounts to promote our latest post”

The notes section is crucial both for the assignee and for the manager.  For the assignee, it orients them before they begin a task. For the manager, is allows quick and easy management of tasks, as it saves them from reading the entire workflow to find out what the task is.

Without a good “notes” section, you’ll find that the task “titles” become very lengthy!

Expected deliverables/results

This field functions as “the bottom line” of the task’s definition. It describes, as clearly as possible, what are the expected results of completing this task successfully, or what deliverable files/products should the assignee end up with.

For example:

“Expected results: a new post is created inside WordPress, including the show notes I wrote, proofread, stylized, tagged, and with pictures”

Another example could be:

“Expected deliverables: Excel spreadsheet attached to this task including the results of the SEO keyword research”

Having the “expected deliverables/results” field is useful both for providing a view of the endgame to the assignee, allowing them to quickly make sure they haven’t missed anything before submitting the task, as well as for the manager – who gets a quick birds-eye view over the endpoints of the task.

Estimated duration

This field is something new that I am implementing. The sole purpose is to give a ballpark both for the manager and to the assignee of how long this task should take. This allows assignees to know if the task is taking too long – and ask for help, as well as helps the manager spot inefficient employees – without needing to understand the task itself.

The reason I am adding this to my documentation and standard operating procedures is that after one of my employees resigned, I had to take on some of his tasks. I quickly found that tasks that took him an entire day, took me 75% less.

How easy it would’ve been to spot this, if my original SOP template included this field? How much time and money could I have saved? A lot!!!

Workflow

OK, this is the meat 🙂 The workflow is the step-by-step, turn by turn, explanation of how to complete the task. This should be (as mentioned above in this post) as simplified and un-technical as possible.

While everything else determines the “context” of the task – who completes it? When is it to be completed? What should be the results of it? – This is the only part of the task actually explaining HOW the task is to be done.

This is the ingredient that creates the consistency and scalability that systems offer, and allows you to stop doing the technical work – and delegate it to someone else!

For example:

1. Log in to MeronBareket.com WP account at http://www.meronbareket.com/mgmt . Use LastPass for login credentials
2. Click on Posts
3. Click “Add New”
4. Insert following post data:
   1. Title: IIP – Draft
   2. Select Category: Podcast
   3. Copy “default code to place in every draft” from the bottom of this task, and paste it in the WordPress post
5. Click “Save Draft”
6. Once the page reloads, click on “Get Shortlink”. Post the shortlink in this task.
   10 … etc.

Task’s “IFTTT”

Just like every task should have “task’s timing”, defining what are the triggers that prompt the starting of the task, every task should have the endpoints defined as well. In other words: for every task, you should define what happens once the task is completed, whether successfully or with error? IFTTT, standing for “if this, then that”, is that endpoint definition.

This is where you define stuff like:

• “if completed successfully, change task status to ‘pending approval'”
• “if completed successfully, Mark task as complete”
• “if you believe changes are to be made to the workflow, contact anyone from the managing team and discuss the issue”
• “if you receive an error message, stop immediately and contact tech support / your supervisor”
• etc.

Basically, IFTTT defined how a task “behaves” in your organizational world, and how it affects other tasks and people. You could define an IFTTT rule that upon completion of a task, the next task in line is assigned to someone specific (thus automating the “trigger” mechanism, instead of having project managers trigger all tasks manually).

Download the SOP template here

Download my standard operating procedure template by clicking here: Send Me THE SOP Template (PDF & Word)!.

You will be emailed a zip file containing both a printable PDF (for those that want to fill in the tasks by hand, or use the printout to draft procedures in staff meetings) as well as an editable Word file. It’s yours for free.

Tools For Creating Documentation And Standard Operating Procedures

In the last part of today’s episode, Ralph and I discussed the different tools that can be used to easily manage the systemization and management of your business.

Recommended documentation tools:

• Google Drive – creating your SOP documents in Google Drive allows you to easily share those documents would anyone around the world, as well as provide an online environment to edit and manage revisions, leave comments, and improve the systems.
• Evernote – you can create a shared notebook, and save each SOP as a note. From this point on it pretty much behaves the same like managing in Google Drive.
• ScreenFlow – every time I need to show an employee how a process is done, I can simply do it on my computer and have ScreenFlow record every single mouse click. This creates a video documentation of how the process is done. I could just as easily ask the employee to convert this to text SOP as well, and save precious time on writing it. The Windows alternative to ScreenFlow is Camtasia.
• Jing or Skitch – both apps allow capturing and annotating screenshots, allowing you to capture screens showing where actions should be taken, parameters to be used, corrections that need to be made, etc. Jing also allows recording short videos, instead of splurging on ScreenFlow/Camtasia.
• Skype + eCamm recorder/Pamela – Skype is an amazing collaboration tool. But if you are already spending the time on getting online with your employee, and showing them how to do something – why not have that call recorded and used at documentation for future employees? Both eCamm call recorder (for Mac) and Pamela recorder (for Windows) allow you to record Skype calls, including video and screen shares, with a flick of a button.
• Internal WordPress site/internal wiki – both of these options provide another way to make your systems available to all of your employees via the Internet or your internal network at a central location, as well as providing editing and provisioning tools.

Recommended project management tools:

1. Asana – Asana is currently my favorite tool. Used by several Fortune 100 companies and entrepreneurs alike, Asana provides a way to build and manage both your SOP’s and projects and tasks all seamlessly in one place. It’s incredibly robust but very agile and takes only minutes to learn. Oh, have I mentioned you get it full-featured for free for up to 15 users? 🙂
2. Trello – a more visual project management tool then Asana. Ralph praised it in today’s episode. Like Asana, it provides an easy way to assign tasks and have conversations around them. Also like Asana – it’s free!
3. Basecamp – one of the world’s most famous project management tools for small companies and entrepreneurs. It isn’t free, and in my opinion a lot less fun to use then the above two options, but does deserve being listed nonetheless.

SOP’s And Project Management Mentioned Resources:

In addition to the resources mentioned above, here are the other resources and books we covered in today’s episode,

• Download your free Standard Operating Procedure (SOP) template
• Happy Someone
• Ralph’s new affirmations app for iOS
• Ralph’s new project – AppYourBiz
• The E-Myth Revisited: Why Most Small Businesses Don’t Work and What to Do About It
  
• The Checklist Manifesto: How to Get Things Right
  
• Inspiring Innovation podcast interview with James Schramko

I Need Your Help!

If you haven’t already, I would love if you could be awesome and take a minute to leave a quick rating and review of the podcast on iTunes by clicking on the link below. It’s the most amazing way to help the show grow and reach more people!

Leave a review for Meron’s podcast!

Affiliate Disclosure: Please note that some of the links above are affiliate links. There is no additional cost to you, and I will earn a commission if you decide to make a purchase.

Don’t Miss an Episode! Subscribe Below:

• 
• 
• 
• 
• 

Using something else? Copy this address:
––– http://www.meronbareket.com/feed/podcast/ –––

In this episode, Ralph Quintero and I dissect ‘The E Myth Revisited’ by Michael Gerber, and see how to apply lessons for the book to real life businesses.

Sometimes the universe throws you a curveball. This week was one of those times. With undeniable irony, right after my previous episode about the systems that drive Inspiring Innovation went live – my VA has announced her decision to resign.

At first, I felt confident that the systems I previously shared with you will allow us to make the transition quick, smooth, and easy. However, an in-depth look revealed that those systems where built around specific people with specific skills, not around the processes that had to take place.

Having a system that depends on the specific abilities of a specific individual is still better than having no system – but not by much.

So I decided rebuild my systems – the smart way. I was obviously doing something wrong, but I wasn’t sure what, so I decided to go back to the book that started the systematization journey for so many of my colleagues and friends: “The E Myth, Revisited”.

The E-Myth Revisited: Why Most Small Businesses Don’t Work and What to Do About It

The E Myth Revisited: Episode Highlights

• Why should you care about systemizing your business.
• Key mistakes that I have made, and how can you avoid them
• why the E Myth has forced me to reflect and remind myself of the true reasons behind starting my business.
• Why until you find and define your primary aim your business will never have good systems that can replace you.
• Why without systems you don’t have a business – but just a glorified job!

Today’s episode is the first in a series of two episodes documenting my transition to (hopefully) better and more scalable systems, following ‘The E Myth Revisited’, as well as advice from my close friend, business mentor, and cohost for these episodes: Ralph Quintro.

It turns out that (like anything else in life), when it comes to building a strong, robust business, understanding where things usually go wrong can prove to be quite helpful in making them go “right”.

So without further adieu, let’s get started… and tackle the elephant in the room:

Why Do Small Businesses Fail?

According to the revisited version of The E Myth, released on October 2004, over 400,000 small businesses in the US close their doors every single year. Considering the current state of economics, and the fact that 10 years after the book has been published, the failure rate hasn’t changed too much – this number is probably higher today than ever.

According to Michael Gerber, the author of ‘The E Myth’, most entrepreneurs held a technical job before they set to launch their own business. I had one, and chances are you had one too.

Whether you were an:

• IT professional
• graphic designer
• a salesperson
• a plumber
• an accountant
• a doctor
• a nurse…

…Or a teacher, engineer, hairdresser, or anything else – chances are you are doing something technical, and that you were damn good at doing that.

But while you were great at what you did, something wasn’t right.

Maybe you hated your job, your colleagues, your boss, your customers, your hours, your dress code, the commute, or anything else about the job. Whatever it was, one bright day, something snapped inside of you. “I’m not carrying on with this shit anymore!”, you found yourself shouting (probably inside your own head).

That moment right there (recognize yourself in that picture?) is what Michael Gerber (the author) calls “the entrepreneurial seizure”. According to Gerber, this is the real reason why most people decide to start their own business and become entrepreneurs.

Oddly, this is also the number one reason why most people fail at creating an amazing business.

Most of us start a business simple as a legal way to kill our boss and get him out of our lives.  So, we usually take the technical things that we already know how to do well, and build an entire business around those things. According to Gerber, most entrepreneurs and small business owners end up recreating their job, just without the part that pissed them off.

But here’s the problem with this approach: a business isn’t just about the technical work that needs to get done. A business also requires us to complete managerial tasks and take care of stuff that is perhaps out of our “technical comfort zone”, like:

1. Sales
2. Marketing
3. Managing employees
4. Customer support
5. Financing…

… And a lot more.

As Gerber puts it:

“rather than [knowing the technical work] being [your] greatest single asset … [It] becomes [your] greatest single liability”.

By taking the technical job that you did for someone else, and creating your own business around it… You have successfully cloned both your job, as well as tens of other tasks that other people (even if you disliked them) used to do.

Many new entrepreneurs say to this: “I know, but I can do that job better, too”. And perhaps they’re right. But more often than not – the technical job in a new business takes so much of their time, that they never reach all the things that they can do better than others.

It’s impossible for one man to do all the technical work as well as the managerial and entrepreneurial work. There is no way to do everything, and like anything else in life, something has to break.

Bottom line is that most entrepreneurs default to do only the technical work, neglecting everything else… because they don’t have the time to do it. 

The result? An entrepreneur working around the clock in his business, instead of ever working on his business. And so, he can never truly break free, and the business becomes more limiting and consuming than the job he once ran away from. Overworked, under slept, tired, frustrated, and in worse case – in debt.

The REAL Problem With The E-Myth (The Entrepreneur Myth)

We all know the entrepreneur myth. We grew up on it. Hell, I promote it on this show:

The single individual, whom surmounted all of his powers and against all odds, struggles, hardships, and forces of nature – made it to the top. 

How? Well that’s the mythical part of the story.

The mythical entrepreneur who won against all odds.

 The myth tells us that the success is achieved with cutting edge innovation, a burning passion and desire to succeed, and many, many hours of burning the midnight oil. The myth holds the hard work of the individual as the most sacred, and while all mentioned above IS REQUIRED, what’s missing here is working on the right things, and doing so at the right time.

What Are The “Right Things” That Entrepreneurs Should Work On?

• Building a business that serves a need of your customer… rather than your need of getting rid of your boss.
• Building a business that’s scalable and can carry on providing consistent experience to your customers as it grows.
• Building a business that provides you with the lifestyle you dreamed of when you left the 9 to 5 job… rather than a business where you always need to put in twice as many hours as you ever did in corporate!
• Building a business that frees you to pursue the things that matter most to you… instead of repeating the technical tasks time after time, project after project, to no end.

The only way to achieve these things, which according to ‘The E-Myth’ are the true benefits of entrepreneurship, is to awaken parts of your personality that might have been dormant for a long, long time.

Waking Up Your Dormant Entrepreneur

According to Gerber, when it comes to business, there are three different people that live inside of us at any given moment. In order to understand who these people are, and why they live in our brain rent-free, let’s start with an example (taken from the book):

Fat Guy VS. Skinny Guy

Imagine every single time in your life where you decided to go on a diet, get back to shape, or start running. What were you doing a second before that idea flashed through your mind?

Personally, I get the urge to take better care of my health and of what I eat when I find myself stuffing another Snickers bar down my pie hole while watching Sunday night football.

“Jesus Christ, this is the most I ever weighed in my entire life! I get breathless just from walking up the hill when coming back from the supermarket! I really need to get my shit together!!!”, a voice says inside my head.

You know what I’m talking about, right?…

…That voice is skinny guy.

Skinny guy is all about health, fitness, vegetables, yoga, and all things that revolve around… well, being skinny. Skinny guy is the voice in our head that makes us go to the sports shop and buy a new pair of running shoes, running clothes, heartbeat monitors, and whatever other accessory that will start collecting dust in our cupboard pretty soon.

But before our new running accessories get some wear and tear, we usually wake up one morning to find that someone else in charge: fat guy.

Fat guy doesn’t like running. Fat guy doesn’t like the gym. Fat guy doesn’t like cold weather, or hot weather, or any weather for that matter. What fat guy wants, is to stay in bed, or maybe crawl to the sofa and watch some TV while eating nachos.

And as long as fat guy is back in charge, you return to your previous habits (those that woke up skinny guy to begin with).

Do you recognize the struggle between skinny guy and fat guy? Most people do. Since only one of them can be in charge at a given moment, one’s fitness rises and falls on the ability to balance the two.

So what does all this have to do with entrepreneurship? 

In ‘The E Myth’, Gerber explains that just like the never-ending battle between skinny guy and fat guy, when it comes to business we have three different people trying (and failing) to get along together inside our brain:

The Technician

The technician is the business persona that most of us recognize most easily. As already hinted in this post, the technician is the one that’s getting things done.

The technician does the “actual” work. He’s the part in us that believe that, “if something needs to be done well, then only I can do it.”. And he’s the voice inside our head forever reminding us to “get back to work”.

Only lives in the presence, the technician doesn’t bother himself with neither the past nor the future… he just wants to clear his to-do list!

The Entrepreneur

The entrepreneur lives in the future. It’s the part in us that gets excited about opportunities and “how things can turn out”. It’s the part that asks, “wouldn’t it be great if…?”. It’s the part of us that gets hooked on ideas and envisions the marvelous business we could build out of them, and the impact that would have on our lives.

The entrepreneur is always wondering how things could be made better, but has no regards to the past or present. He lives in the future and spends no effort dealing with the problems that are currently “on the table”.

Give the entrepreneur total control, and you’ll find yourself working at daydreaming rather than anything else 😉

The Manager

The manager is the part in us that likes order. When you find yourself shopping for boxes at home depot, and later rearranging your entire garage into those boxes… you know the manager guy inside you took control.  The manager is the part in you that gets excited by the concept of using a label maker (don’t be ashamed, I love my label maker!).

If the technician lives in the present, and the entrepreneur in the future, you could say the manager lives in the past. He is in charge of reflecting, analyzing, and making sure things would go better the next time. In a way, he’s always cleaning up after the entrepreneur.

Come to think of it, without the entrepreneur, the manager will have nothing to do. And without the manager, the technician doesn’t know what to do, and when to do it. And finally – without a technician, nothing would ever truly get done.

Looking at it this way, it’s pretty obvious that you need all three of them in order to create a successful business. But just like Skinny Guy VS Fat Guy, only one of these personas can be in charge at a given moment. So the problem becomes balancing the three.

Since most of us are used to being “the technician” in our 9 to 5 career, we usually let him take control of everything, not leaving room for the other two. BIG MISTAKE.

As you can see, as long as the technician is running our business we will always be stuck on the hamster wheel.

The technician inside us will never build systems for other technicians to follow and replace him, because, “who has time for that?”. And so… Most entrepreneurs struggle with building a business that lets them grow and break free.

Does Your Business Need To Change?

According to the book, I would say there are three major reasons for you to decide to change your business, and they are:

1. Financial reasons
   • Is the business making enough money to cover the bills?
   • Is the business making enough money to grow?
   • Is the business making enough money to create the lifestyle you dream dull when you started it?
2. Freedom reasons
   • Has the business become nothing more than a glorified job?
   • Is the lifestyle that the business provides you actually worse than what you had in the old days of the 9 to 5?
   • Do you have less vacation days than ever, and spend any waking moment thinking about your business?
   • Is the business unable to function without you?
3. Life aim reasons
   • Is the business helping you achieve your life aim goals?
   • Is it creating the change you envisioned, both in your life, your family’s life, and in the lives of your customers?
   • Does it look and behave like what you wanted it to?

If you answered “no” to any of the above, you, just like me, could benefit from today’s episode, as well as from reading ‘The E Myth’. 

Scroll to the top of the page and click “play” to listen to today’s episode – you will find out how to move forward from this point and towards creating change. Or come back in a few days for part two of my The E Myth review!

Until part two… Be amazing,
Meron

P.S. What did you think about today’s post/episode? Agree? Disagree? Leave your thoughts in the comments section below… I’d love to know 🙂

Mentioned Resources:

• The E-Myth Revisited: Why Most Small Businesses Don’t Work and What to Do About It
  

I Need Your Help!

If you haven’t already, I would love if you could be awesome and take a minute to leave a quick rating and review of the podcast on iTunes by clicking on the link below. It’s the most amazing way to help the show grow and reach more people!

Leave a review for Meron’s podcast!

Affiliate Disclosure: Please note that some of the links above are affiliate links. There is no additional cost to you, and I will earn a commission if you decide to make a purchase.

Don’t Miss an Episode! Subscribe Below:

• 
• 
• 
• 
• 

Using something else? Copy this address:
––– http://www.meronbareket.com/feed/podcast/ –––

Photo credits: A drowning man’s hand – © Elenathewise – Fotolia.com.  Mad man – © olly – Fotolia.com.