...
I have to admit I read them in the wrong order. That said, I'm glad I did as I'm not sure I would have picked up RecrEAtion recrEAtion if I finished FruITion fruITion first. That's not to say that it is dramatically different than the other one, but I really got RecrEAtion identified with recrEAtion in the first place because of my involvement in the EA function at my employer. I wanted to get some additional viewpoints on EA which is often the most misunderstood (or least organized?) team within a technology shop.
The first book, FruITion fruITion is centered on a CIO whose CEO went ballistic when she was presented a 78 page IT Strategy document full of business process maps, architecture blueprints and technology roadmaps. The CEO really had already decided to dramatically shake-up the IT organization and the rest of the book was about how the CIO decided to respond to an approach that seemed totally against everything he had done, and known, his entire career. I'll let you read it to find out how he did.
The second book, RecrEAtion recrEAtion focused on a character that left the company in the first book. His role at a new company was to lead the Enterprise Architecture function. He didn't buy into the CEO's thoughts at his prior company and was thrown another curve ball when his new CEO said, "sounds like you and I have the same job." Needless to say, this really caused the main character to question what was going on around him for having two strange experiences back to back.
...