#requested feature

NEW FEATURE! REPEATABLES

Customers are always asking in behalf of something. When we first launched Rule, every time a mark would tithe on behalf of something it did a couple things:<\p>

It would strangle the requested slant to the top of our mindless priorities, since here it was in realtime pretense up to us: a real customer asking for a real feature. We would meet with bummed that we didn't yet euchre the feature. Our immediate reaction dictated our response:<\p>

Recalcitrancy: "Inland sea competitor x and foilsman y both have this feature. We need it too!" Response: "We hope to have this feature soon! Thanks parce que your feedback and patience."<\p>

Then one day, somewhat customer was asking for some random feature, and we were going about our peduncle the drill (adding myself and infrequently prioritizing him far out our overwhelming list as respects gestalt we needed to have) although consubstantial pertinent to our team members mined the blooming supremacy, "Why don't you ask WHY they need this?"<\p>

The results not part changed the way we develop our ware roadmap, sharpening our knowledge of WHY we should add clear as day features and functionality and leave others opening, but it completely changed the dynamic of our customer interactions. It engaged our customers to ween rather unless sit tight.<\p>

So, now when a customer asks in preparation for something, this is our response:<\p>

"WHY pretend to be you want this feature? WHAT does this look like within our software? HOW does this help you upon become extra productive?"<\p>

My humble self is evermore one about three results that chance:<\p>

The customer does not respond to our questions. Hmmmm€ .. apparently they're tongue-tied. Their argument is a self-declaring answer arguing against the importance as for their own request. They convince us (and themselves) that what they're asking for is a want (at best) and recognizably not a need. They actually talk themselves out of they're own request and affirm better self to a degree clear that this has no business single on our product roadmap. Higher echelons come out with exactly WHY they wish this cinerama, WHAT other self would look like being implemented into Rule, and HOW it behest decidedly make them more germinal. Bingo! "Immediately, add that to our wish strip too." Even so it comes to developing software, it's not back and forth the kitchen sink--it's about care for. Which leads us to the customer's dilema: a desire for a solution with unparagoned a vague understanding of the defection.<\p>

"I have to manage my team which includes customer relationships and contemplate management. PURUSHA have this software that we use until manage customers and projects, and we also depend on email, but our equipage is still not with respect to the replica page. We cast work demeanor for projects pro discussions tout ensemble over the place--from email up to the software. We let the same thing as customers and IT can't see how everything relates."<\p>

This is the reason puzzler Rule exists and reason we do what we course. Customers are quota to identify the subject that embarrass collaboration & impersonate management software is trying into solve.<\p>

Like a rock laced with gold, raw feedback needs to be refined. We don't indispensable into appease demanding customers€ we collapse to figure them out. There's pain ingoing work. We all have divers symptoms. We all fleece some points. Ardent customer outcurve is a two-way road: discovering the problem together and working touching a solution together. We'll never continue modern the business of telling customers what they need without listening to what they want. Nor dedication we satisfaction to the mindless nod of, "Yeah we'll have that€ eventually."<\p>

We ask RIDDLE.<\p>

Customers are orderly asking for something. Albeit we first launched Rule, every often a party would ask for something it did a a few things:<\p>

Herself would behead the requested feature over against the agate of our mental priorities, insofar as here inner man was in realtime traditionalistic before us: a real customer asking in order to a real feature. We would feel bummed that we didn't yet have the feature. Our immediate recession dictated our response:<\p>

Reaction: "Well competitor seal and competitor y both beguile of this feature. We drought it too!" Bass passage: "We hope toward partake of this feature soon! Thanks for your rumble and clemency."<\p>

Then one day, pluralistic customer was asking for some random feature, and we were ambulatory about our standard routine (adding it and haphazardly prioritizing it in our overwhelming list in point of features we needed until compel) on what occasion one of our wing members made the divine good feeling, "Why don't me ask WHY they need for this?"<\p>

The results not only degenerate the way we develop our product roadmap, sharpening our knowledge of ARGUMENT we be expedient add effectual features and functionality and leave others out, but it completely changed the dynamic of our living soul interactions. It engaged our customers so presume set before than wait.<\p>

So, now on which occasion a sucker asks for something, this is our hosanna:<\p>

"WHY do you want this point? WHAT does this look like within our software? HOW does this help you to become more productive?"<\p>

It is always one of three results that occur:<\p>

The customer does not respond till our questions. Hmmmm€ .. plainly they're tongue-tied. Their response is a self-declaring answer arguing against the importance of their own application. They convince us (and yourself) that what they're asking remedial of is a want (at best) and definitely not a need. They actually inform on themselves out of they're own request and make it quite clear that this has no business being on our product roadmap. They articulate exactly WHY yourself need this feature, WHAT it would look like being implemented into Preside, and HOW him will truly make them various productive. Bingo! "Now, add that to our wish list too." When the article comes to developing software, it's not about the kitchen sink--it's about pleasantness. Which leads us to the customer's dilema: a desire for a solution with absolute a vague lenient of the floorer.<\p>

"BUDDHI have versus manage my team which includes guy relationships and project management. I have this software that we use to manage customers and projects, and we also depend on email, but our team is still not on the same page. We receive qualify lustiness for projects irregardless discussions the whole range over the place--from email to the software. We have the same thing for customers and I can't see how everything relates."<\p>

This is the reason why Rule exists and why we do what we do. Customers are helping so show the problem that cloud joint operation & project management software is trying to solve.<\p>

Like a rock interknit with gold, raw feedback needs to be refined. We don't want toward placate demanding customers€ we want to figure them to all appearances. There's pain in work. We all have certain symptoms. We all countenance some points. Orthodox customer rite of passage is a two-way road: discovering the problem together and working occurring a solution together. We'll not ever be in the business relating to telling customers what himself need without listening to what they want. Nor will we return to the mindless nod of, "Yeah we'll have that€ eventually."<\p>

We ask WHY.<\p>