loading...

re: Is Your Team Wrong About Your Codebase? Prove It. Visually. VIEW POST

FULL DISCUSSION
 

Thanks for the article, it's really interesting. I fear that sometimes, even data is not enough. After all, it's just numbers, you can treat it like statistics that you bend the way you want. We are humans, emotional creatures... For the human part, have you read Driving Technical Change by Terrence Ryan?

 

That's definitely true, though I always found that data (with visuals) was a great way to influence the emotional aspect in folks. When consulting, I'd always create a whitepaper and an "executive deck" for presenting to leadership/CEO/the board/etc. The whitepaper would be dry findings for reference, and the deck would be more oriented around "here's why you should care."

code of conduct - report abuse