How we work
Form follows function
Where we start
Toscas Group works from core principles and organizes around the need, deciding what team, tools and structure the problem calls for.
We work out what the job has to do before we decide what form the work takes.
We apply the same six principles to every effort, and what we build from them changes with the problem.
Six principles
Understand the problem.
Each person sees a different part of the problem. Finance sees a cost, operations sees a delay, technology sees a system, and the customer sees a wait. We walk all the way around it before we decide what to do.
Organize around the problem.
We let the problem decide the team, the tools and the structure, and we do not presume what the answer will look like before we understand it. This yields a truly cross-functional effort.
Technology serves the business.
Over twenty years in technology we have learned that technology should serve the business and not exist for the sake of itself, so we work out how the operation should run before we choose the technology for it.
Success is found in implementation.
We believe the success of any plan is found in its implementation, which is why we stay past the plan and do the work ourselves.
Success is user understanding.
A solution nobody uses has not been delivered. We train the people who will run it until they understand it and can do the work without us.
Clients are partners.
We sit alongside the people we work for and act as their owner's representative, the one who speaks for the client's interests with every vendor and contractor.
The tractor in the field
A country borrows money to buy tractors. A few years later a tractor is rusting in the field, and someone is farming by hand right next to it.
Nothing was built to support the purchase. We have watched the same thing happen with technology in businesses and community organizations, and it is why we plan before anyone buys.
Read. Write. Execute.
The principles become work in three steps.
Discover, interpret, organize.
We start with the north star: why the organization exists, in one idea. Then we learn the problem where it lives: on the floor, in the systems, in the books, and from each person who touches it.
Strategize, plan, define scope, build.
We design the answer and put it on paper: what to keep, what to cut, what to buy, what to stop. This is also where we build the organizational model to address the problem: the right application of people, tools and partners, and no more.
Implement, test, refine, measure, manage.
We carry it out in the way the work calls for. It may run as a project with a fixed end, as a program across many projects, or as a product that we improve in rounds. We tell the people it affects what is changing and when, and your people validate each stage as it lands. We train them until they understand it and can run it, because a solution nobody uses has not been delivered. Then we stay to ensure results stick.
We take the form the problem needs.
Depending on the problem, our team organizes as one of these:
A seat
We place one experienced person in your team.A team
We build a group for a defined scope.A program office
We run one team that coordinates many projects, vendors and sites under a single plan.A standing role
We serve as your owner's representative or part time technology executive (a fractional CIO), month after month.A product
When the answer to one client's problem would serve many others, we build it as a product and run it.A firm that owns only a hammer
tends to find nails.
Our roots are in technology, in networks, systems, software and data that we built and ran with our own hands, and we could have stayed there. Some firms treat technology as an island. We have always treated it as a tool, and a tool is only as good as the job it is chosen for. So it was natural to bring other tools into the fold as problems called for them: the balance sheet, vendor management, training, communications planning, brand and product. We pick the tool after we understand the problem.
Bring us the problem.
We will tell you what form we think the work should take, and what it would cost.