Book Image

Data Fluency

By : Zach Gemignani, Chris Gemignani, Richard Galentino, Patrick Schuermann, Nathan Yau‚ÄØ
Book Image

Data Fluency

By: Zach Gemignani, Chris Gemignani, Richard Galentino, Patrick Schuermann, Nathan Yau‚ÄØ

Overview of this book

Analytical data is a powerful tool for growing companies, but what good is it if it hides in the shadows? Bring your data to the forefront with effective visualization and communication approaches and let?Data Fluency:?Empowering Your Organization with Effective Communication?show you the best tools and strategies for getting the job done right. Learn the best practices of data presentation and the ways that reporting and dashboards can help organizations effectively gauge performance, identify areas for improvement, and communicate results. Topics covered in the book include data reporting and communication, audience and user needs, data presentation tools, layout and styling, and common design failures. Those responsible for analytics, reporting, or BI implementation will find a refreshing take on data and visualization in this resource, as will report, data visualization, and dashboard designers.
Table of Contents (20 chapters)
Free Chapter
1
Foreword
12
Titlepage
13
Copyright
14
Dedication
15
About the Authors
16
Credits
17
Acknowledgments
18
End-User License Agreement

Designed to Be Used

By Ken Hilburn

I have become curiously interested in a recent blog post that talks about how it’s difficult to correctly write an application for the iPhone. The assertion is that writing software for the iPhone is harder than for a desktop, not because of the technology, but because everything counts so much — every design choice, every line of code, everything left in and everything left out.1

Very eloquently and precisely put. If you’ve ever used any sort of mobile computing platform, not just the iPhone, you know how much proper design can make an application really useful—or totally useless.

But then again, isn’t this the case with any application? Some applications seem to have their genesis in the charter “build an application that allows the user to perform all these actions,” whereas others are built on the charge “build an application that helps the user solve this problem”—...