A 30-hour journey with your team can yield without pesky barriers.

All day long, ideas run through your head.

Will this work? What if that process is tweaked? Can you make things more efficient, more cost-effective, speed them up, rev their engines? Or, as you'll see in the new book, Sprint by Jake Knapp, John Zeratsky and Braden Kowitz, is there a better way to conquer the meeting rat-race?

What happened at the end of your last brainstorming session? Chances are, nothing. Great ideas floated around, there were arguments and a few silly suggestions. But, if you're honest with yourself, not much got done.

In his job at Google, Knapp brainstormed a lot, too, but when he realized that doing so was ineffectual, he began to tinker with the problem-solving process. He calls his new method a "Sprint," and it starts on Friday, when you invite seven people to wipe their calendars and join you Monday morning.

Ask a "Decider" to come, and don't forget the "Troublemaker."

At 10 a.m. on Monday, "you'll start at the end," Knapp says. What's your goal? What answers do you need? You'll make a map for your quest-then, after lunch, you'll begin talking with experts who have "special knowledge" on the issues related to the problem you have.

Tuesday morning, you'll start to find solutions by reviewing what's already on the table, "to remix and improve." Bring paper and sticky-notes on Tuesday; you'll need them for jotting down questions that come to mind. Your team facilitator will also need to start searching for customers.

On Wednesday, you'll create your storyboard. On Thursday, mock up a prototype. And on Friday, you'll test your product.

Having endured my share of non-problem-solving "problem-solving" meetings, I was eager to learn how a Sprint can change the entire system. Quickly, I was rewarded with a happy moment: Only a handful of people are involved in a Sprint. No more wasted time and no more warm bodies just taking up space.

Sprinting, according to Knapp, is a step-by-step, no-dilly-dallying method to get things done in about 30 hours.

And yet, what's inside Sprint isn't as easy as it looks. Knapp advises lots of prep time. Even so, doesn't a new problem-solving method seem worth a try?