Reduce: To Improve

February 5, 2015

Reduce: To Improve

This post is about progressive reduction, which is what I’ve recently read about. From what I have gleaned, progressive reduction is about those gradual changes (mostly reduction) in the UI elements that relate to your time-lapsed incremental cognition of a product. In other words, progressive reduction is in continuously adapting the UI elements of your product based on the gradual improvement in its usability. Read the full post.

Rate this:

Technical Writing

Buyer Behavior, Customer, documentation, Insights, Methodology, progressive reduction, quality parameters, reduction, TechComm, technical communicator, User

Posted by:

Suyog Ketkar

He is a certified technical communicator. He believes that writing continues to be an easy-to-do but difficult-to-master job. In his work time, he proudly dons the “enabler” cape. In his non-work time, he dons many hats including one of a super-busy father.

2 responses to “Reduce: To Improve”

Rahul Khare

February 5, 2015 at 3:53 pm

The camera analogy said it all. Well conceptualized and expressed Suyog.

LikeLike
1. Suyog Ketkar
  
  February 5, 2015 at 4:31 pm
  
  Thank you, Sirji, for the appreciation.
  
  LikeLike

About Me

I am a writer by passion and profession. I eat, speak, and sleep writing—although, not always in the same order. My work journal enlists sales, writing and editing, and technology stints. I can adapt to changes, and learn from challenges with the curiosity levels of a baby. I like to share stories—as if you hadn’t guessed that one yet. When I am at my work desk, my team knows me for my translation skills: I translate complexities into solutions. I authored and published The Write Stride – A Conversation with Your Writing Self in 2017 and The Dogfight and the Lone Peacekeeper in 2021. Both books are available on Amazon.