Every team needs an agile process. Or two.

Maybe some teams can get by without strictly following documented processes every day, but when it comes to agile software development teams, it’s simply not an option to operate in the dark.

Since software is complex and easy to mess up, processes mean the difference between a great product and a crappy one. Without processes, software teams will spend more time squashing bugs and dealing with support headaches than they will actually developing the product…

The exact reason we created Process Street is to help businesses avoid that nightmarish cycle, and, of course, we use Process Street ourselves to help run the agile processes behind the scenes.

We use regular agile processes like:

• Daily standup meeting
• Sprint planning
• Sprint turnover
• Sprint retrospective

We also run routine QA processes like:

• GitHub pull request procedure
• Weekly WordPress maintenance
• SSL certificate renewal

And, finally, we have a set of training processes:

• Developer onboarding
• How to set up your development environment
• Pull request review failed procedure
• Pull request merge procedure

These are all regular tasks for the team, and the reason they were created was because we found they have a high margin for error.

Scroll down to find the exact processes we use.

If you want to tighten up the way your software team works, hit your sprint targets, and efficiently train new development hires, then this post will show you how. We even reveal the exact processes we use and a workflow diagram detailing the journey an issue takes from start to end.
Continue Reading

The 5+ million people who work in HR in the HR HR processes are hard and complex.

From hiring great-fitting talent and helping with their onboarding, to monitoring employee performance and even resolving any employee conflicts, there’s a lot of ground for HR teams to cover – and in such a short amount of time.

Imagine if there was a way for HR teams to time-save, cost-save, labor-save, and take control of their recurring tasks like never before…

Wouldn’t that be a dream?

At Process Street, we rather like turning dreams into reality. That’s why we’ve hand-picked our most effective, most useful HR processes from our extensive library and are presenting it in this ultimate HR process pack.

Think of it as your one-stop-shop for all the human resources processes you’ll ever need:

• Why use workflows for HR processes?
• HR processes #1: Pre-hiring processes
• HR processes #2: Hiring processes
• HR processes #3: Onboarding processes
• HR processes #4: Performance processes
• HR processes #5: Workplace processes
• HR processes #6: Diversity processes
• HR processes #7: Aptitude tests
• Create your own HR processes with Process Street today!

Now, let’s stop dilly-dallying and get to it!
Continue Reading

Are you in need of some workflow examples to make your teams smarter?

But what makes a team smart?

Several things do, but powerful workflows are one critical ingredient which makes teams smart.

Teams that use workflows don’t set goals and simply hope to reach them; they create checklists (workflows) to make sure they reach their goals.

No wonder 50% of businesses that use workflow management systems say the results are substantial.

It’s incredible.

Teams that use workflows are super organized and able to perform daunting tasks — no matter the long processes involved.

But what types of workflows should you be using this year?

It’s different for every organization; workflow systems are not always one-size-fits-all. But these nine Process Street workflow examples should give you inspiration for how you can build important systems to run your business with.

Our workflow examples:

1. Employee onboarding workflow
2. Customer support workflows
3. Customer onboarding workflows
4. Content marketing or writing workflows
5. Podcast publishing workflows
6. Request and approval workflows
7. Travel workflows
8. Content promotion workflow
9. Standup meeting workflows

Continue Reading

Would you agree to fly on a plane knowing that the crew was simply ‘told’ what to do but didn’t use clear guidelines and instructions?

Probably not.

Sadly, that is how many organizations operate today – without realizing that it may result in a wide range of negative consequences, from employee inefficiency to lost customers and profits.

Telling employees what to do is not nearly as effective as having a set of written step-by-step instructions they can follow, explaining how exactly routine operations should be performed. That’s where standard operating procedures, or SOPs, come in.

Continue Reading

British Airways chief executive described the incident as “catastrophic” as 800 flights were canceled and 75,000 travelers were affected.

Flight compensation website flightright.com estimated that British Airways would have to pay around €61m to passengers for refunds alone under EU legislation. Add to this the cost of reimbursing angry passengers for unexpected hotel stays and other inconveniences, and the total financial damage to British Airways has been estimated at £100m.

Why? Someone turned their data center off and on again.

The entire airline was down for almost 2 days. This wasn’t a natural disaster, it was a process failure.

In this article, we’ll explore how to spot process failures before they occur using a system called Failure Mode and Effects Analysis (FMEA). We’ll assess an overview and then delve in deeper to ground our understanding and include a premade Process Street FMEA template to help you run your own assessments in future.

In this article we’ll cover:

• Your free FMEA (Failure Modes and Effects Analysis) template
• FMEA? What is Failure Mode and Effects Analysis?
• When do we use FMEA?
• Conducting and documenting Failure Mode and Effect Analysis: A user’s guide
• What happened to British Airways?
• Why did it happen?
• How can FMEA help us prevent this happening again?

We send out feedback requests to new blog subscribers so we know what kind of content to write that will be the most useful. Sometimes, the answers surprise us.

In particular, I often get awesome responses that give me insight into how our customers plan and create their processes:

One reader plans out their processes in a spreadsheet because columns make it easy to build the steps out. Another said they analyze a Trello board of tasks and lists to make sense of how a successful project was executed, then writes a process to recreate those steps. And, of course, we have our suggested ways that we have found our customers have the most success with.

In this post, I’m going to go through four methods you can use to document processes accurately, quickly, and naturally.

1. The minimum viable process
2. Turning an archived Trello board into a process
3. Mapping a process in a spreadsheet
4. Turning a screencast into a process

Let’s look at each method in detail.

Continue Reading

This post is a collaboration between our Process Street Team and Corey Fradin, Founder of QuickBooost. Exploring topics like productivity, time management, and goal setting, QuickBooost helps you better utilize and take control of your time.

The pursuit of productivity is often simplified to a hero’s fable involving the conquest of willpower; the reality might be more about the systems we build around our work, and the clever things we do to make work easier.

You only have 24 hours in a day. You can reduce the problem of productivity to: How many tasks can I get done in that 24 hour period?

What you choose to do with your time – which tasks you prioritize, which you choose to delegate, which you choose to automate, all of these factors are directly the result of the productivity system you build around your work.

You already have a productivity system, you just might not realize. Even if you don’t feel productive, you can still look at what you’re currently doing and understand it in terms of some kind of system.

What that means is, you can break the situation into parts, like your goals, objectives, strategies, and tactics; how all of these things work together amounts to your productivity system.

Take for example David Allen’s Getting Things Done methodology. The GTD method is basically the idea of achieving mental focus by writing down your main tasks, and figuring out how you can break them down into smaller, more immediately actionable tasks.

This is a type of productivity system.

So, in this article, we’ll be looking at:

• What a productivity system actually is
• Why productivity systems are important
• How to build a simple productivity system
• Best practice tips on how to be productive
• Continuously improving your productivity system
• Extra productivity resources

In essence a productivity system is a lot like a straightforward process that helps you break down your workload into smaller, more manageable chunks, and ultimately do more work, more efficiently.

Continue Reading

At Process Street, we’re all about process optimization: creating, implementing, analyzing, mapping, improving, and automating.

There are a lot of layers to processes and it’s easy to get caught up in the complexities.

But really, it’s quite simple.

You need to document your workflow and then follow it, making improvements where necessary over time; continuous improvement.

All of this can be summed up by the concept of process optimization.

In this Process Street article, we’ll give you a quick actionable overview of how to optimize your processes with some tips and tricks of what to look for and how to do it.

We’ll cover:

• Process optimization basics: What you need to get started
• The business process optimization workflow
• How to work out the goals of your process optimization
• How to optimize processes with automation
• Process optimization resources to get started now

Bidding for jobs can be cutthroat.

Not only do you have to create an accurate estimate of how much everything will cost, but you have to do so as quickly as possible to have the best chance of securing the customer.

You don’t want to waste time filling out forms when you could be working, but any mistakes can severely damage your chances of getting the sale (if the estimate is too high) or even ruin your reputation (if the estimate is too low).

That’s why we here at Process Street have created and gathered these 14 free estimate templates.

Instead of having to create your own job estimate form, all you have to do is look through the templates below and see which one you like best. All serve the purpose of giving your clients a professional job estimate document, but allowing you to just fill in basic details instead of creating each document from the ground up.

Just head for one of the following sections and make your pick:

• General free estimate templates
• Microsoft Word job estimate templates
• Microsoft Excel estimate templates
• PDF estimate templates

Processes are a lot more interesting than you’d first think. That isn’t some kind of joke — they’re interesting, I swear. But what is a process?

Although they’re defined as “a collection of interrelated work tasks initiated in response to an event that achieves a specific result”, there’s a bit of a backstory that helps us cut through the corporate tranquilizers and understand what a process is, and why processes matter.

First, a few examples of processes:

• Cleaning the store
• Finding an email address
• Deploying software
• Customer profiling
• Onboarding a new employee
• Planning a wedding

But why are those processes? Why aren’t they just jobs to be done? The point is that when you formalize a process, you think about the workflow with productivity in mind and it makes it easier to execute and optimize.

Continue Reading