Pulp Innovation Chapter Seventy One

I met the crew from Marlowe Innovation for lunch that afternoon at the Brown Derby. The cool late October sun made me wish for my gabardines and a wool overcoat rather than the business suit I was wearing. But I was following the consultants precepts - never dress worse, or much better than, your customer. And Accipiter was an old-line, suit and tie kind of place, where my lack of sartorial splendor was never an issue among the man in the gray suit fashion statements.

We were right where I thought we'd be at Accipiter, three months into an eight month engagement with about two months worth of work complete. That didn't alarm me much, since the lethargy and inertia that forestalled much action was starting to change. Either we'd energized the beast and it would move more quickly, or we'd startled the beast enough to make it panic. Then it would show us its teeth for certain. Only more work would tell if the new acceptance of our work was based on agreement or was merely laying a trap and waiting for us to fail.

I saw Matt in our favorite booth, with two cold, frosty adult beverages and one long slender iced tea. I started right in for the squat mug, assuming the tea was for Meredith, who usually didn't imbibe over lunch. Matt raised his mug to me in a mock salute and quaffed a fair portion while I did the same. Meredith entered a few minutes later and we took time to recap our work loads and plan the next quarter. Matt and Meredith were fully up to speed on my work at Accipiter, and I tried to avoid talking about it as much as possible.

Meredith told us about some new ethnography work she had just won at a new client. There's nothing better than new work, unless its also new work with a new customer. The client, a medical services company, wanted to understand unmet and undiscovered needs in its customer base. Spotting a possible opportunity, I asked Meredith about another service.

"Are they at all interested in innovating around the customer experience?"

She hardly blinked.

"I've already teed up some work on customer experience journey mapping, and I think they'll be very interested in it."

We didn't hire her just for her looks.

"We're going to kick off an ethnographic study with some of their customers and patients, and evaluate behaviors and actions to understand if there are some unmet needs. Those will become need statements that we'll have Matt use to drive some idea generation with their team. Once that work is complete, we'll have a chance to pitch them on some customer experience journey work, but I'm concerned about trying to do both at the same time."

Matt nodded. "Two different approaches for two different needs."

"Yep, and since they are a new client, we need to demonstrate some value before enlarging the scope of the work. Great job."

Meredith was clearly pleased, but Matt and I had already thrown out our shoulders slapping ourselves on the back for bringing her in. She had added a crucial capability to our team and had attracted new work on her own. My only concern was whether or not she realized how valuable she was to our little firm.

"How about you Matt?"

I knew what Matt was working on, and who he was working with, just as he knew about my trials and travails with Accipiter. You can't be partners for over a decade without great communication, but I'd found that a short discussion always led to new insights or opportunities.

"Still working with Conover on some new idea generation, and they've asked us to deliver some innovation training to their mid-level managers. I think over time they could do a great job managing the idea generation internally, but it will be a few more months before they are fully trained."

"We're seeing a lot of requests for innovation training."

"Yes, I think firms are starting to realize that with the right tools and methodologies, they can bring in house a lot of the work they've outsourced to the bigger consultancies."

"You think they've finally realized how important innovation is to their businesses?"

"No, but they are starting to realize that innovation can be a competitive advantage and they want more innovation more frequently."

We were well stocked for opportunities. In fact, if the work at Accipiter kicked off well, we'd probably need to hire another consultant or two if we could find some to fit in with the merry band.

"Reach out to your contacts, both of you. See if there are people you know you'd like to bring aboard, especially strategic folks and people with a background in training."

Meredith and Matt both nodded. I think they were happy, and I was pleased to see Marlowe growing.

Pulp Innovation Chapter Seventy

While I'd never compared it to digging ditches, real thinking work is hard work, exhausting work. I've heard that the brain is basically a leach, sucking all the energy and nutrients from the rest of the body, but after a full day of scenario planning I had to believe it. I was drained. Wiped out from a full eight hour day in a Herman Miller Aeron chair in a comfy conference room.

We'd finally managed to agree on our strategic scope and had started collecting market information, industry trends and other information we felt would be helpful in building scenarios. One of the biggest challenges was to extend our line of sight beyond one or two years. It seems that no one in the aerospace group (and I suspect no one in Accipiter) had done any long range thinking for years. And by long range, I mean three years out. So we had quite the battle royal over creating scenarios that were more than five years into the future.

"The future much past three or four years is almost unknowable" Greg said. "We don't know enough about that timeframe to predict it effectively."

Greg had a point, but it didn't hold water with me.

"Do you plan to be in business three to five years from now?"

"Well, of course."

"What products and services will be important to customers in five years? What can you effectively and profitably deliver? What key needs will those customers have?"

"I think they'll have many of the same needs as they have today. As for the changes that may take place, we can't know what those are, and building products or services based on hunches is risky."

"We don't work on hunches, we work on educated guesses based on trends and their likely outcomes. For example, we can see already that the Asian economies are rebounding faster from the downturn than the US and Western European economies, yes?"

He nodded, not wanting to commit much more.

"Ok, if that's true, and if Asia depends on air traffic to move people around and air freight to move goods around more than these other economies, we can predict that there will be an uptick in demand for new planes and for replacement parts in Asia in the next two to three years at a minimum, and if their economies grow more rapidly than ours over the next five to seven years, the demand there will far outstrip demand here."

There were nods all around the table now.

Greg shrugged. "OK, but what do we do with that insight?"

"All we've done so far is begin to create a scenario that suggests that the Asian economies come out of the downturn faster, and we've begun to identify implications of that scenario. If they grow faster and maintain a higher growth rate than Western Europe and the US, the demand on air traffic will increase dramatically. That was already the fastest growing market for air travel, especially long range air travel and air freight. If we predict those markets to grow rapidly, we should begin to identify new products and services we need to create to support that growth and win market share. We also need to think about how our services are structured and where we have people on the ground. It may make sense to start shifting resources to Taiwan and Singapore, since we already have operations there."

"But what if that scenario is wrong? What if we've placed too much emphasis on Asian market growth?"

"That's why we create several competing scenarios about the future." I noticed that Greg no longer seemed to have as great a concern about the timeframe. Now he was worried about chasing the wrong story, rather than the length of the story. "We need to create another scenario based on other trends that we've collected. Perhaps we have a set of trends that suggests that there will be a significant reduction in military spending since we'll reduce wars in Iraq and Afghanistan, and the world is eager for a "peace dividend" again. In that case, governmental spending on aircraft and maintenance will plunge. That's a realistic scenario based on the trends we've captured, and would have a huge impact on Accipiter unless we find ways to deliver new services. Perhaps in that scenario Accipiter takes on the role of mothballing and maintaining planes in the desert."

Greg shook his head. "That's all interesting but almost too much to wrap my head around."

"The point of scenarios isn't necessarily to be able to predict the actual future, but to identify discontinuities and anticipate them, and bring new needs or opportunities to light. None of these scenarios is exactly right, and several of them overlap or intersect. It's just as likely that our Asian scenario and "peace dividend" scenario are partially right. If so, we need to either change our government services or exit those and move our focus to Asia."

Everyone on the team had their eyes glued on Greg. If he bought in, they were mostly on board. If he rejected the approach or timeframe, Susan and I had a lot of work to do to get the team back on board with our approach.

"We can either assume the future will look a lot like today, and plan new products and services based on the needs and demands we believe are valid now, or we can try to understand what the potential futures are and anticipate those needs. That's innovation" I said.

Greg nodded. "OK, let's finish the Asian growth scenario and flesh out the "peace dividend" scenario. I think there are one or two other scenarios to consider."

With that we were off and running into the future.

Pulp Innovation Chapter Sixty Nine

Faulkner said that the past isn't dead, it's not even past, or something along those lines. I suspect if he'd been interested in innovation, rather than examining the mores of southerners after reconstruction, he'd have had a similar pithy statement about the future. Perhaps something like "the future isn't unknowable, just uncertain". One of my favorite authors, William Gibson, has a line that reads "the future is already here, it's just not widely distributed." By which I think he means that we are the future, just becoming aware of it at different rates.

When you work with trends, and develop scenarios to try to ascertain the future, you and your team work in a nebulous, ambiguous void where everything is possible. By conjuring just the right insights you may be able to identify opportunities before anyone else. But turn the broth the wrong way and you've created a picture of the future that is unlikely to occur. Scenario planning is where we first start separating the true innovators from the administrators. There's simply too much ambiguity for some folks, and they demand clearly drawn "black and white" lines. Sorry, that's not going to happen. And if you thinking developing scenarios based on a five to seven year time horizon and five to ten key trends is tough, wait until you try to tease out wants and needs from an ethnographic study.

No, the reason Trend spotting and scenario planning is one of the first activities in our work on innovation, beyond the obvious need to understand the future, is to quickly ascertain what the team can, and can't, or won't do. I'd rather face up to it now that some of the team may just not be cut out for innovation work, and if they struggle to create a simple story about the near future, they'll be a boat anchor to the rest of the work. Scenario Planning never fails to identify one or two people who seemed promising on the surface but can't, or won't, extend their minds beyond what they "know" is true and factual. If innovation was based on knowable facts, then it wouldn't have any risk involved. Perhaps Altshuller addressed that in one of his paradoxes. I'll have to brush up on my Russian to know for sure.

About a week into the scenario planning it was clear that most of the team was on board and comfortable with the tools and techniques, but Ann Livingstone was really struggling. Of course Ann came from a pure engineering background, which meant she was either going to be perfectly suited for innovation (the discovery part of engineering) or it was going to be an obstacle for her (the rigidity and "finding the one right answer" part of engineering). With Ann, it was all about the black and white. She struggled mightily and hampered the team's progress because she simply couldn't accept an unknowable future, or was trying to juggle too many unknowns in her mind. Two equations, two unknowns, a solvable problem. Five questions, seven unknowns, not possible, therefore no reason to try.

Ann clearly didn't come from what I like to call the handgrenades and nuclear bomb sort of engineering (close enough for effect) but came from the bridge-builder school of thought. I'm thankful that many engineers are worried about making sure the bridge stays up, and stays put, and can endure the forces thrust upon it to eight standard deviations. However, that kind of thinking conflicts with innovation thinking, and it was clear Ann was hurting the team. Susan and I were going to have to adjust Ann's methodologies and thinking, or ask her to leave the team.

"Will it damage the morale of the team to have Ann leave so quickly? she asked.

"I frankly think Ann's participation is damaging and holding the team back, and the rest of the team resents it."

"How do we let her go gracefully?"

"I don't think it would be a surprise to Ann for us to ask her to play a different role. Her skills are going to be much better suited for evaluation and product development instead of innovation. We just recast it as a better fit downstream."

"OK. Do we backfill her role now?"

"I'd like to have another engineering representative, but perhaps we should interview the candidates rather than have them assigned."

"Thompson won't like that. His aerospace team is already stretched."

"well, we'll find out from Gregg if it is more important to mollify Thompson and have a gap in our team, or if it is more important to have a fully stocked team and a slightly steamed Thompson."

"I'll talk to Ann in the morning."

"Take it from me" I said "she'll be relieved."

She was, and the rest of the team was as well.

Pulp Innovation Chapter Sixty Eight

Three weeks, four days and two hours into our project, we finally started doing innovation work. Forming, norming and finally storming, we'd built the team, addressed their concerns and were finally at a place where we could do some real innovation work, rather than build the team, assess the participants, address their (realistic) concerns and define a project plan. We were finally going to do some scenario planning. There was just one problem.

We were meeting in the innovation team room, formally known as Conference room 2A, on a cloudy Tuesday morning. Susan was facilitating the meeting, our first effort to start looking further into the future of the aerospace business. It was at this point we realized that no one on the team knew exactly what the future looked like, or understood any of the trends that might shape that future. The parable of the blind men and the elephant from Kipling was top of mind.

"We've never really paid a significant amount of attention to trends, especially over a three or four year time horizon" said Sally McKay. Sally had joined the team to provide market analysis for our work. "We typically buy information from industry analysts and compile yearly forecast of market conditions, but we've never looked at bigger trends that would shape the industry over a several year time horizon."

"OK. Let's break this down and make it simple. We want to know what the significant trends are that will influence and shape the market for aerospace production and parts in five to seven years. Typically, when we at Marlowe do this work, we look at trends in four categories: demographic, technological, governmental and social. Who can help us understand the unfolding trends in those four buckets?"

James Davidson chimed in. "We have a chief economist who works with our CFO. He could probably provide some economic forecasts to help us understand some governmental and economic trends."

Susan nodded. "Accipiter also has relationships with several lobbyist firms that can provide insights and trends on federal government regulations and governmental actions, at least within the US. We'd need to find firms or analysts that can provide insights into foreign governments and their actions, since our parts can be used in a number of countries."

I looked at James and Sally. "Surely you have relationships with industry analysts who can provide forecasts and trends as pertains to technologies in the aerospace industry?"

"Yes, and we can go talk with the guys in R&D. They are constantly experimenting with new technologies and capabilities, and they attend a number of engineering conferences. I think we can get them to give us their insights."

"OK, that covers economic, governmental and technology. Our team can put together trends that encompass social and demographic changes over the next five to seven years that will impact the aerospace industry. Let's look at the flying population and how that will increase or decrease. Let's look at the green movement to see how that will impact recycling, or reductions in waste, or fuel consumption in the airline industry. There are a number of social and demographic factors that may influence how planes are used and built. Remember the massive Airbus plane? The one that was forcing international terminals to build new jetways for, because it is so large? The demand for that plane has fallen as the economy has dipped, and the price of fuel has increased. We need to think about that plane and consider all the factors that will influence the future."

So, with a few assignments everyone went off to gather insights from their respective sources. Susan and I had a few minutes to reconnect and plan for the next meeting.

"How frequently will we need to gather these trends? This is going to be a fair amount of work, and some of the team will run into resistance since the people they'll be talking to won't understand how we'll use the data."

"Ideally, trend spotting and trend gathering would be an ongoing, sustaining process, not a discrete activity. In this case I know we won't continue the effort, but we need to demonstrate the importance of gathering this information and assessing it regularly."

"That's a lot of work, and a lot of data."

"Yes. But if Accipiter can do it well, you'll have the ability to assess your future opportunities and challenges and a much longer runway to decide what you want to do. It's not that difficult, and not that expensive, and can create really valuable opportunities."

Susan shook her head. She agreed, but I think she realized how big the change would be for Accipiter. When you have a small army, you have to pick which battles you want to fight. Was this a time to dig in and fight, or a place to retreat and reserve our forces?

Pulp Innovation Chapter Sixty Seven

They say the word sabotage was created when the Dutch would throw their clogs (sabots) into the works of mills. Every innovation project has it's saboteur, usually well meaning but very disruptive, and I'd been waiting for the shoe to drop. On a crisp morning not long after our meeting with Greg, the spanner, or shoe, went into the works.

James Davidson joined our innovation team from the aerospace product marketing team. He was eager, interested and full of ideas. He also had a full plate of work in his day job, which must have been important but uninteresting. The shoe fell on a day when we were moving ahead on our strategic planning and preparing for some trend spotting and scenario development. We'd just finished our plans and identified the meetings and workloads.

"Um, I have a problem" he said. I glanced at Susan, who glanced at Greg, and we all waited patiently for James to spit it out.

"Go ahead" said Susan.

"Well, how are we supposed to get all of this innovation work done? I mean, I still have a job, and my boss is on me to make sure I get my regular work finished. I'm finding it tough to balance the demands already."

"We're just getting started" said Susan, and James nodded. "The workload for the innovation team will only increase. This work is in addition to your day job."

"I know, and I volunteered for this project. But I can't end up worse off in six months because we created a cool new product but I didn't get my other work done as well as it should have been done."

"Good that you are voicing the concern now" I said. I glanced around. Of the eight of us on the project, only Susan and I were "full time". Everyone else still had some component of their regular jobs. Greg seemed unfazed, but everyone else seemed sympathetic to James' complaint.

"OK, how many of you have concerns about getting this project done well and keeping up with your day jobs?" All the hands went up, except Greg's.

There were only a couple of realistic responses. We needed to gain some cover for these folks who were innovating, and if possible relieve them of more of their day job responsibilities. We also needed to change their incentives and compensation to place more emphasis on innovation. Those were some big changes, but I didn't want to have to play the CEO card just yet.

"Greg, let's get Jane from your HR team in here. We need to place more emphasis on innovation in the evaluations and compensation structures for the team members, or at least work with the team to reduce their work loads so we can innovate successfully. My preference would be to tweak the evaluation and compensation models so people who demonstrate innovation activity and success don't get dumped on at promotion and bonus time." Greg nodded. So far he was steady as a rock when we needed it.

"OK James, if we can work to divert some of your work, and perhaps add some points about innovation in your evaluation, does that give you the cover you need to stick with the team? We probably can't totally relieve your work load, but Greg can talk to your manager and we can ensure you don't end up worse off for having participated on this project. What do you think?"

James paused, but realized he'd probably gotten all he was going to get.

"It's not perfect, but I want to be on this project. I think it matters to Accipiter. Hopefully, if we can create some great new products and services, any work I miss will pale in comparison. I just don't want to end up worse off because we are innovating."

Heads were nodding like naptime in a kindergarden. No one else had quite the guts as James, but they all felt the same way. The shoe had dropped. Everyone wanted to know that they would end up at least as well off in their positions and careers regardless of the outcome of the project. If they didn't get that assurance, we wouldn't have to worry about wooden shoes in the gears, they'd vote with their feet. They'd miss meetings on innovation to attend staff meetings. They'd fail to review ideas because of their "day job" demands. Slowly but surely the commitment would leak away and we'd be holding meetings with ghosts.

I knew what we needed, and I suspected Greg did too. He stood up.

"OK, I hear you. I'll work with your managers to ensure everyone ends up after this project is over in at least the same situation if not a better one, and no one will get dinged for working on this project. You have my word on that."

His statement was like a breath of fresh air, or perhaps the escaped sighs from the team members merely felt like a breeze. It seems as though every one was holding their breath, and Greg hit the right notes to allow everyone to relax and recommit.

Pulp Innovation Chapter Sixty Six

Making decisions is easy. I make them all the time. Blue socks with the blue suit. Steak for dinner. Single malt after. Even a child can make decisions. Making good decisions with limited knowledge that have a lot of impact, there's the rub. And what the aerospace group needed were clear, concise decisions about innovation targets.

I couldn't help but feel for Greg. After all, I've been unfortunate enough to watch a number of executives twist on their own petards. It's easy to say "we need more innovation" but often hard to say, specifically, what we should be innovating. Making decisions and choices is as much about what to leave out, as to what to leave in. Making the decision meant making choices that would impact the organization for months or years, coming down on a strategic direction. Making the decision meant success or failure in the not too distant future. No wonder most firms can't innovate. They can't make good, informed decisions and communicate those things to their staffs. Something about plausible deniability.

We met with Greg a week or so into the project. We had selected a team, not necessarily everyone we wanted, but workable. We'd talked to the communications team and we had a program ready to alert the aerospace group that we'd be focusing on innovation and needed their attention. All the major pieces were in place, except possibly the most important piece. What were we going to focus on?

"New products" said Greg. "We need new products. We're getting our heads handed to us by foreign competition. Even our best customers are telling us that we've fallen far behind. We need something really revolutionary."

"Do you have any customer insights or requirements developed? Has your sales team discovered any interesting unmet or unarticulated needs? What about innovating around the way you service and support your products? Does it have to be a new product, or one that's delivered or serviced differently?"

"AXT has released a number of new products that are much lighter, but as strong and resilient as our older products. They are cutting weight from the plane, and that equals less fuel burned per mile. Nippon Air Industries has a completely different approach. They offer to maintain their products right on the tarmac. Their products are probably equivalent to ours in terms of weight and performance, but their maintenance is superb and cuts costs and time for the carriers. Whether our solution is new materials, new products or new services is almost a moot point. We need it all, just to catch up to what our competitors are doing."

"So, really, we could be just as successful innovating around a business model, or a service offering, or even the customer experience? What do you want to prioritize, Greg? That will give us focus for the team."

"My preference, because it's something we can do quickly, is to create some new products for the industry with really outstanding and revolutionary capabilities - extremely low weight or extremely easy to maintain or extremely long life. I think Accipiter can drive new product development faster than it can wrap its head around new services or business models."

Good. One key focus area down, with hits about how radical or disruptive the change needs to be.

"Do you want to conduct this as a "skunkworks" and separate the team, or open the work up more broadly to the entire aerospace division? I think we can move faster and we'll be more likely to achieve radical ideas in a small, separate group, but we may miss some good ideas from the division if we don't involve them."

"No, I'd prefer to keep it smaller. I've read about Lockheed and the skunkworks model and that's what we need right now. Small team, fast action, radical outcomes."

"Great. So we can assume that we'll form the team and keep the idea generation within Accipiter. No "open innovation" models - at least not with the Accipiter name. If we need to use some external innovation, we could leverage a company like Innocentive, perhaps?"

"I don't want to create a lot of publicity, but there may be inventors or entrepreneurs we need to tap externally. Tell me more about Innocentive?"

"Innocentive helps connect people with ideas to people with needs. Basically we can place a notice that we're trying to solve a specific technical problem, and anyone who is registered on their site can spot that and submit technical solutions to the problem. There are two nice things about Innocentive's services: first, most of the people on the site are engineers and technologists, so we're likely to get relevant responses, and second, we can post anonymously."

"But we're not ready to post anything yet - correct?"

"No. And we'd use them only if we weren't satisfied with the ideas we generated or felt we could go further by including that capability."

"OK - do you have what you need? A fairly radical product innovation developed by a small team that has a lot of leeway and flexibility but works primarily internally. Don't focus right now on services or business models. I just don't think we're ready for that."

"This helps a lot. As strange as it may sound, offering very specific instructions in some dimensions of the challenge encourages innovative thinking in the areas we leave "unbounded". And an innovation effort with no scope just becomes an attempt to boil the ocean. We've got enough for now."

It went even better than I had hoped for. Greg was under the gun and ready to make decisions, since many of them had been made for him and Accipiter by the competition. Nothing sharpens the mind like a near and present threat.

Pulp Innovation Chapter Sixty Five

There are a number of impossibilities in life. You can lead a horse to water, but you can't make him drink. You can lead a teenager to class but you can't make him think. You can't push a string uphill. To add to that litany, you can't tell people often enough, and in enough detail, about dramatic change like innovation.

In every innovation project I've worked on, I've preached the theology of communicating about innovation - it's goals, purposes and outcomes. Almost uniformly, my requests go ignored or unanswered. I'm not sure if the management teams don't want to talk to their folks, or are afraid a big communication efforts commits them to actually doing innovation work. Inevitably, we'll run into a significant portion of the workforce who is unaware of the innovation focus and effort, and needs insights into what we are doing and why we are doing it. Typically, at the end of an innovation effort, a senior executive will turn to me and say "that went well. Too bad we didn't do a better job getting people on board earlier." As sure as the sun rises in the east, and Sisyphus is pushing that rock, I'll live through another project where we fail to communicate effectively and regret it at the end. Accipiter was proving to be no exception.

Greg was actually on board to communicate to his team, but felt he needed to pull in the corporate PR team to help write the communications. After several missed meetings and delays, Susan and I convinced him that we could write the communications, but we would need help to select the most appropriate channels. In my work, we've managed to use a wide range of communication vehicles to educate and inform, including emails, newsletters, voicemails, taped video of senior executives doing the talking head thing, posters, table tents in the break rooms and a host of other activities. Susan and I had pulled together a relatively comprehensive program to communicate to the aerospace group, but we felt we needed the PR team's blessing and their final polish of our messaging. We'd even written up some talking points for Greg's reports, so they could talk about innovation to their reports and stay on message. Now, we just needed to get the internal communications team on board. No easy task.

We met with Leslie Parks, the VP in charge of internal communications for Accipiter. We'd been warned that Leslie was very proprietorial with her communication team and channels, and that we'd need to build a case for communicating. In fact, I found her very open to the fact we wanted to communicate the changes we were planning, but very concerned about the volume of communication in general.

"We'd be happy to work with you" she said, and I felt it was sincere. "But what we need to do is balance your messaging with all the other messaging that's going on. Right now many Accipiter employees are overwhelmed with internal emails and communications. We've just finished a big push for HR and benefits, and have another messaging and communication campaign about to start for the United Way. I understand the requirements and urgency of your work, but you also will want our employees to read and understand your messages, and with the volume of emails going out to them right now, I can't assure you that will happen."

"OK. What if we break our communications down into three targeted groups - executives, senior and mid-level managers and the rest of the staff? Most of our direct communication needs to go to the first two groups, primarily within the aerospace group. We also need to communicate a broader innovation effort more generally across the company, but our first targets will be within aerospace."

"Your talking points for the executives and senior leaders look great. I'd like to pass them through our review team to ensure they don't conflict with any other messaging. I think the managers will like this and use some of the draft emails and talking points to communicate to their teams. Do you have an intranet site or some other website set up where people can visit and get more information? Emails are great, but a permanent site that people can review as they are interested is very valuable."

In fact we did have plans for an innovation website, but the development of that site was currently IT project number 347, somewhere after the rollout of a new SharePoint site for time management and before the development of a blogging template for internal bloggers. In other words, we were probably going to have to build an external blog site in the short term.

"We're working on that" Susan said with a wry smile. "We'll have something ready within the next two weeks."

Leslie agreed to work with us to include our communications into the Accipiter communications calendar, and promised us feedback on our plan and talking points within a week. That would give us enough time to build at least a sample blog site to provide some insights into the Accipiter innovation process. As for the internal site development, we were still waiting on approval for hardware and trying to find the staff to do the work.