Business processes, business technology, online marketing. I am Phil Ayres, 20 years in enterprise software and business improvement. And blogging on and off since 2006.
Friday, April 01, 2011
Justifying business process improvement without being a fool
Wednesday, October 27, 2010
Fix the little things, and get big results
Wednesday, July 28, 2010
Old approaches to business process management are failing companies
- methodology - the way a company can fix its problems
- technology - applications helping people work in a more structured way
- reduce headcount
- do more work with the same resources
- improve the quality of a product or service
- treat each customer as an individual rather than force fitting them into a standard model of a customer
- allow the processes that serve customers to extend and adapt based on circumstances
- help the business owners introduce new improved processes rapidly and with minimal cost
Monday, May 24, 2010
Despite Twitter, email is still where we communicate
I have a love-hate relationship with email. For tracking work and tasks to be performed, especially in common workflows, email sucks. For communicating with people, the 'offline' nature of email is perfect, since you can send a message and that message will sit and wait in the recipient's inbox until they get a chance to read it. At the other end of the spectrum, Twitter and Facebook feeds just can't claim that: the messages are so transient that they are more like watching TV or listening to the radio, so if you weren't staring at the screen when a post came through, it is likely you'll never know about it.
So my renewed love of email (over social networks, at least) was given a little spark by the news that Constant Contact (don't claim you have never received a newsletter or event invitation from a company using them, because I won't believe you!) acquired Nutshell mail. Why is this interesting to me, or you? Well, quite honestly Twitter and Facebook really start to stress me out when work/life balance skews itself in the 'work' direction. I want to follow what is going on in the network of my friends, associates and the companies I follow, but keeping my head in an application like TweetDeck is unreasonable and a terrible distraction. So the idea of getting a notification email summarizing everything that has happened in my social network world, that sits there until I'm ready to decompress a little and read it, seems like a great idea. Finally, there is a better chance that I will not miss the last minute wedding announcement from a certain friend the far side of the world (you know who you are...), and that I will not miss another VIP announcement related to a local event that my small business is sponsoring. This is what Nutshell mail can offer, a nice summary of what is going on in your online social world, in a consumable email, ready to read when you are ready to read it.
So I still think that email sucks for work that people do in offices that is routine and repeatable: HR recruitTell him its about self-promoing; employee onboarding; travel expense claims; account payable and invoice tracking; new customer account opening; and so on. If you do these types of work regularly, you don't want the tasks getting lost in your email inbox, the same way as you don't want to have to stare at your Twitter and Facebook feeds all day long to know what is happening that affects your business or makes your sales efforts generate more leads. Email is great for less distracting communication, since it isn't just the Twitter equivalent of a crowd of people standing in a room shouting and waving 'HEY, LOOK AT ME!'.
I'll be interested to see where Constant Contact takes Nutshell Mail. It seems like a great addition, as it puts important messages for you where they should be: in your inbox. This ties in really nicely with the process improvement work I do with companies, where we work to free up employee's email inboxes by taking the routine work out of them, leaving the inbox to do what it does best: hold messages you need to know about but can deal with later.
A post from the Improving It blog
Edit ... OK. So the scoop is I'm married to a senior-ish person at CTCT. I'm not being paid for this blog post (the obvious pay-back is no more than you'd expect - and a whole pile of chores to complete at the weekend). And if you have read my blog before you'll know that this post is as relevant to the constant information sharing (and subsequent self-promotion) that is a blog such as mine. There you go - official cya declaration done. Oh, and the second declaration is that as much as I enjoy the concept of Facebook and Twitter, they really do stress me out. But please do follow me anyway at http://twitter.com/consected
Cheers, Phil
Tuesday, April 06, 2010
Improving processes as companies merge
Mergers and acquisitions can lead to chaos at the best of times, with inconsistent processes and un-integrated teams. Can business process management (BPM) or general workflow automation help in M&A related organizational integrations, or is it just money being thrown into an inferno of change?
BPM marketing often uses words like 'agility' when describing how your processes can be adapted to respond to change. Agility implies an ability to dodge new requirements and keep ahead of the chasing threats, all requiring constant attention from Management to work. I prefer a process improvement solution that is 'flexible' and can absorb the impact of unexpected actions and requirements, automatically taking on the new shape required by a rapidly changing organization.
In a chaotic organization, there is the temptation to avoid process improvement, since it is too much to handle and things are changing too fast. Despite this, bringing structure to the processes that enable a company to operate is essential, whether there is chaos surrounding them or not. With a strong starting point, a department can not only run its own operations better, it can start to influence the organizations with which it interacts. In an M&A scenario, having a solid base of process can make it more appealing to retain that backbone of operations in the new organization, rather than defaulting to the typical political decisions for what stays and what goes.
The problem is that traditional BPM takes a significant time and investment to implement, which is rarely a possibility when approaching M&A. A better approach may be instead to consider a 'quick and dirty' fix to the key processes that will be interacting with the new organization, in the knowledge that everything will change anyway. To be successful, the 'quick and dirty' approach needs to also be flexible (that word again), to adapt to the constant change around it, rather than just collapsing by being too brittle.
Picking the right technical products to build your solution is one part of it. Collaborative technologies, like wikis are great for sharing information in a loose team with minimal effort, but they don't help reinforce processes that require repeatable operations and decisions. Business rules management may be better for processes that rely on complex decisions that must evolve over time, where the end-to-end process is limited in length. BPM is fine where there is rigidity and constant repeatability required and you have time to put it together. Software as a Service (SaaS) or prebuilt solutions running in the cloud can help to get things up and running faster.
I think that companies need a combination of all of these, even when they are not in the chaos of M&A. And rapidly built solutions using flexible blended applications may not be a bad approach to follow.
A post from the Improving It blog
Let us help you improve your business today. Visit www.consected.com
Tuesday, March 09, 2010
Lean + BPM = no big surprise
As I have been working more with process improvement professionals that practice lean methodologies, I thought I would put down my thoughts on what 'lean' means to the office / services companies that are typically customers of business process management (BPM) tools. I'm sure for anyone involved in 'lean' already this will sound like a very rudimentary definition; for that I apologize. This is really an attempt to try and communicate the value of applying lean manufacturing techniques to BPM projects, for customers that have not yet delved into one or the other. To me it seems that the combination of lean and BPM is really nothing new.
Lean Production / Lean Manufacturing has been refined by manufacturing companies, building on decades of experience running ever more efficient production-lines. Without the constraints of a physical production-line, office and services businesses often struggle with improving their business processes, typically falling into the trap of deploying ever more complex enterprise software. The benefits of lean methodologies can be experienced by businesses without a huge software investment and lengthy implementation projects; of course, a solution is required to help guide work as it flows between the activities performed by different people in an end-to-end business process.
As some vendors start marketing the benefits of Lean Business Process Management (Lean-BPM), it is important to remember that the design of new and improved processes with BPM and workflow tools has always incorporated aspects of lean methodologies:
Remove waste from the process
- convert manual delivery of paper documents to automated delivery of electronic work cases
- prevent repetitive email of requests lacking appropriate information to template work requests guiding the entry of all information
- handle manual allocation of work by supervisors to team members automatically, allowing supervisors to focus on delivering value as experts rather than task-masters
- reduce the time-lag between activities especially for priority work, by instantaneous delivery of work to the next available person in the process, allowing a critical series of activities to be completed faster
- remove the need for rework by implementing solutions that guide people to completing their tasks correctly first time, also improving quality of the work product and customer perception
Continuous improvement
- provide the capability to measure the performance of processes with real business metrics
- identify issues and areas of waste in a business process with easily reviewed information
- allow business users and analysts to make changes to a process without burdening IT or requiring software development skills
Lean-BPM is a marketing term, not a standalone methodology. A company almost certainly needs software to help improve an office- or services-based business process. If you follow the advice of experienced lean practitioners you will avoid committing to over-complex BPM and enterprise software tools and their extensive software projects at the outset, until you have a better idea of whether they will offer real business value to your to-be processes.
A post from the Improving It blog
Let us help you improve your business today. Visit www.consected.com
