Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

60%
+1 −0
Q&A How to leverage social proof?

The key is to establish a strong foundation first. Someone who is resistant to change will need to see why change is necessary, how it can be accomplished easily and cheaply, and then feel the pres...

posted 12y ago by Kit Z. Fox‭  ·  last activity 5y ago by System‭

Answer
#3: Attribution notice added by user avatar System‭ · 2019-12-08T02:23:44Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/5758
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by user avatar Kit Z. Fox‭ · 2019-12-08T02:23:44Z (almost 5 years ago)
The key is to establish a strong foundation first. Someone who is resistant to change will need to see why change is necessary, how it can be accomplished easily and cheaply, and _then_ feel the pressure of "all the cool kids are doing it."

If you don't establish the reason why change _must_ happen, then social proof will look like flash-in-the-pan.

I would suggest first demonstrating the advantages of the new over the old, and then the benefits of adopting the new practice which comes at the modest expense of a tiny little paradigm shift.

Once you've established a sensible and strong argument for the adoption of the new practice, _then_ you can leverage social proof as additional support.

> CVCS has been the standard since it became necessary to do something other than copy material to a dated folder in the "Backup" file. However, methods of software production have changed since CVCS was introduced 20 years ago, resulting in performance bottlenecks and cranky people wasting time on the nets while waiting for their code to be ready. DVCSs solves the classical frustrations of CVCSs, such as avoiding merging hell and commit races. The adoption of DVCS creates a versioning environment that is more natural for workers, resulting in geometrically increased productivity and infinitely scalable cooperativity. Training workers to use the new format takes less than a week, and once adopted, it quickly becomes intuitive. They can version in their sleep.
> 
> Many sensible, knowledgeable, and successful people have already recognized the genius of this plan. They shag frequently with beautiful, famous, and wealthy people. We recommend you adopt this practice as well, since everyone will be doing it in the future.

What you want to do is establish why this is a good practice, how it can be adopted especially by people who are familiar with the old practice, and then give a little peer pressure. That way, the reader will feel more like they will be on the cutting edge rather than just jumping on the bandwagon.

#1: Imported from external source by user avatar System‭ · 2012-05-25T12:45:16Z (over 12 years ago)
Original score: 7