Categories: Podcast

Designing Better Processes to Get Things Done

In this podcast we consider how to design better processes and contemplate alternatives to a business process that will achieve certain criteria

The Rudolf Podcast is a podcast by Rudolf Olah covering technology, leadership, project management, web development and more.

If you want to be a high performer in your field, you have to optimize your processes.

Transcript

Hey there listeners! Welcome to the latest episode of the Rudolf Podcast! Today we’re going to be talking about how to design better processes to get things done.

When you work on a project, you can break it down into steps. Let’s take the example of writing an article. You would break that down into three steps. Step number one is researching the information and facts and statistics for the article. Step number two is creating a first draft. And the third step is reviewing and refining that draft.

Now let’s try a different approach to writing an article. We could do a little bit of research and then write a paragraph. Then we can do a bit more research and write the next paragraph. And then, we can go back and revise the first paragraph.

In the first process for writing an article we have the three steps of researching, writing and revising. Now in this second process for writing an article, we have an iterative loop of researching, writing and revising. Each step in the second process is each individual paragraph with the final step being the completion of the article.

Now, which process is more efficient? Which process is better designed? Well, it depends on what you’re trying to achieve.

If you’re trying to achieve scale, and have the resources to hire a team the first process design is better. You could have, let’s say, five researchers conducting research for many articles, and a whole newsroom of writers putting the facts together into many articles. Then you can have a few editorial staff to help edit and revise and refine the articles before publishing. It may take a bit longer to write the article but the trade-off is worth it. You will have multiple articles ready.

If you’re trying to publish your article quickly, the second process is better. In this process you write a good first paragraph with great research and publish it. Then you can add more information and refine the article further. Most news sites and blogs do this in order to deliver breaking news fast.

I used writing an article as an example but designing a better process can apply to web development teams. For instance, the idea of a full stack developer who can write both frontend and backend code has gained popularity. On top of that they’re expected to be web designers. However, this can be inefficient for larger teams, where specialization leads to more in-depth knowledge and possibly faster development.

If you want to be a high performer in your field, you have to optimize your processes.

Think about your business and personal life. What processes are you using to get things done? Choose one and try to design a better, more effective and maybe more enjoyable process.

  • Is there a way to make whatever process you’re optimizing more efficient or less stressful?
  • Is there a way to split up that process so that it can be delegated to others so you can scale up?
  • Is there a way to batch many small tasks that are part of the process so you can maximize your time?

Think about these questions and take a bit of time to examine and improve your processes to get more things done. And with that, check out NeverFriday.com for more articles and information on project management, leadership, web development and more. Thanks for listening to this episode of the Rudolf podcast.

Rudolf Olah is a software development expert with over 8 years of professional software developer experience. He has produced the video courses "Reactive Programming in Python with RxPy, PyQt5 and Tornado" and "Learning AngularJS Testing" for PacktPublishing. Rudolf offers web development training courses for individual developers and for web development teams. He writes about tech leadership, career coaching and project management.