Do you do Barely Repeatable Processes?

BRP One is a fully operational and ready to go system to run any Barely Repeatable Process.

All work is sequential in one form or the other, always a process. Either Easily or Barely Repeatable - ERP or BRP:

• Easily Repeatable Process
  
  Usually recognised as "processes". Supported by three letter acronym IT tools - ERP, CRM, SCM, HCM, etc. The mere presence of such solutions (arguably) have made many people processes much too rigid and linear for their own good.
  
  A type of process that is behind approximately 20-30% of world wide value creation.
  
  
• Barely Repeatable Process
  
  "Practices", knowledge worker, manual processes, ad-hoc or exceptions. Activities that seems to be all over the place, the core processes of all service companies and organisations. It's basically what you do every day, seen as a "process".
  
  Supported by meetings, business rules, budgets, deadlines and a few IT based ones like email, phones and online meeting or collaboration systems. The only process oriented IT solution is BPM (Business Process Management), still built on old methods and principles thus being (arguably) much too rigid for it's purpose.
  
  ERP is a subset of BRP, if a system can do BRP it can do ERP, but not vice versa.
  
  A type of process that is behind approximately 64-75% of world wide value creation. And barely touched by IT.
  
  

All Barely Repeatable Processes goes through the same four phases. Reality is much less complex than generally accepted:

Initiate, Mature, Convert, Implement - quite parallel to Boyd's OODA loop - Observe, Orient, Decide, Act.

This is what BRP One does - run the full BRP without any limits and with full flexibility:

1. Initiate (Observe in OODA):
   
   The trigger, the source of activities, the initiator of what we do: An idea, a request, an issue delivered by a co-worker, a supplier, a customer or anybody.
   
   Observe and gather information from the source. Or in the case of BRP One; let the participants add the "Topic" (idea, request, issue...) of their choice.
   
   
2. Mature (Orient in OODA):
   
   Sleep on it, discuss it, punt it back and forth - let it mature.
   
   Leave the "Topics" (idea, issue, request..) in an easily accessible "pool" to allow free discussion and adding of notes, files and suggested "Solutions". Allow participants to pick up a "Topic" or a suggested "Solution", then add comments or requests to it and punt it to some other participant for further and accountable action - "Please do some research on this.." or "Could you check that...?"
   
   Currently the land of collaboration and social software, email and long meetings.
   
   Maturity is reached when possible future paths of action becomes clear.
   
   
3. Convert (Decide in OODA):
   
   When a "Solution" emerges as the way to go for one or more "Topic(s)"; time is ripe to act and implement said "Solution".
   
   That's when a "team leader" (Project owner) makes the decision and "converts" a "Solution" to a "Project" (implementation).
   
   
4. Implement (Act in OODA):
   
   Any single purpose activity is a "Project"; involving one person or 10,000, a single "Task" or a myriad of tasks and sub-tasks in all kind of sequences. Anything from "buy milk" to "build the largest bridge".
   
   Let the "project owners" (project managers) conduct it all with ease and in full view. Include ad-hoc adding of sub-tasks to own tasks (or any for owners), add more "Task"s to "Project", add notes and files to any task or project, change path and rhythm at any time and let it all be transparent and have no glitches.
   
   

• Last part fully covered by BRP One is the Project phase as every implementation is a project, small or huge.
• Instead of spending time on chasing status reports, writing status reports and updating spreadsheets and MS Project she/he can now sit back and watch it all unfold in BRP One. Real time.
• Not limited to using the baton in full sight of the orchestra the Project Owner can be allowed to add tasks, subtasks and change the path at any time. Again all from the BRP One with instant effect.
  
  

With BRP One you don't have to:

• Use email.
• Go to meetings.
• Write reports. BRP One does that continuously.
• Request updates. All is visible.
• Answer requests for updates.
• Looking for stuff. In email clients, file trees and document handling systems.
• Update spreadsheet and project management tools.
• Spend time with to-do lists.
• Fire up any other software.

Instead you focus on actual work and share it with your team or group or everybody else.

• Thingamy BRP One runs on any operating system (currently compiled on Windows, Linux and OS X) and requires no other software.
• It can be on-premises or in the cloud. We can even run it as a service if need be.
• Install is copy and paste then start.
• Implementation requires, once started, an update to participants via web interface or by import (XML or CSV). Other implementation issues depends on scope - including connection via API to other systems etc.
  
  

• €30 per user and month once up and running to full satisfaction, no binding. Users equals all team / group / department / company users depending on scope.
• Admin has it's own interface for settings and tweaks to/adding of workflows, reports, property fields and more.
• Layout specific files are open and accessible.
  
  

Simple and typical process from idea/issue/request to all done and implemented.

1. Add an idea, a request or issue which starts the process:

	When logged on you'll find all you need: A Task bar with view of my tasks and all tasks and where they are is located upper left. On bottom right you'll find the Reports that you're allowed to see.
	Reports are generated on the fly from raw data real time.
	Click on a report and "activity starters" appear, in context. When adding a new Topic (idea/request/issue) do that according to type or category. All blue texts in all interfaces are links that will expand the object and show all properties and related objects.
	Automatic task generation once you have clicked "Go". Now fill in all the issue/idea/request details and choose if you'd like to add a solution or not now. When done the idea/request/issue "goes" to the Pool for punting around.

2. Sleep on it, discuss it, punt it around, let it mature - collaborate to find the best solution:

Now all are involved Click on the "Topics in Pool" report and all is visible: Expand the Topics (idea/request/issue) and you'll see all information (real time) including any related object like Solutions. For each object you can start small processes like Add a note or Link to a solution. Each user will be given different rights according to his/her role. At this stage you can also send messages to other participants related to Topics and/or Solutions to move things forward.

3. Convert the chosen solution to a proper project:

	Find the solution you'd like to convert to a project, in other words implement it engaging all those you'd need to do that. This right is obviously limited to those who have the Project Manager status. With that the full Project will run without any more activity starting, not allowing anything to fall into any crack or be forgotten until the issue is solved or the bridge built.
	Define the project including descriptions, deadlines and files. As it is a converted Solution it has already inherited information from that.

4. Conduct the project until solution is implemented:

	Set the first task and choose assignee Any project has at least one task. You can start as many as you want in parallel, and when one is finished you are given the option to start another one. In addition you can add a task to your project at any time.
	Accept or decline The assignee will be given the option to decline in which case the assigner will have to reassign. If accepted the assignee can do it as one task or split it into subtasks and assign those (to himself if he wants as well). If he assigns subtasks the same mechanism as above applies: He can add follow up subtasks or even add subtasks at any time, but only to his own task(s).
	Tasks are time stamped and visible to all. transparency and focus on start.
	Full overview so all can see who we're waiting for, and since when.
	Review of task is given to any assigner when task is finished. Option to send back to assignee for more with a note of course.
	Add follow up tasks once a task you assigned has been finished and properly reviewed.
	Conduct the Project with full view of all. Here grouped by status, expand the Projects and see all tasks and subtasks and if they're closed or open in one go. The system sets a Project to finished when all tasks are closed and the owner has no more tasks to add.
	Have your own conducting style like grouping Projects by colour - Red, Yellow, Green - and move them around at pleasure.

If you want to dominate your industry, please feel free to contact me.

Thank You.

Sigurd Rinde

Phone: +33 6 8887 9944, Skype: sigurd.rinde, Twitter: @sig, Email: sig@thingamy.com.