Why You Should Share Your Secrets

Why You Should Share Your Secrets
December 16, 2015

Something I’ve noticed in my five years in the wedding industry is how closely we guard our processes and wedding “secrets.” I vividly remember trying to break into the industry, yet there being next to no resources available for new planners. Of course, there are plenty of certifications out there, but those tend to focus on the technical aspects of running a wedding — not the raw and realistic details of what actually happens. The thing is, I believe that as a community, we would benefit immensely from sharing ideas and experiences. Competition gets a bad rap in the wedding planning industry; the market feels so saturated, so how do we both stand out and protect ourselves from the influx of “new” planners that seem to be appearing on a daily basis? Are you ready for some truth? Because here it is: there are enough weddings for all of us. I promise. I’m a firm believer that if someone isn’t a good fit for you, then you shouldn’t try to force it. That client would be much better off working with a planner that fits their personality and style. If you really stayed true to your brand and planning philosophy, your ideal client would come to YOU. And you know what? There’s only one you. That’s why I feel it’s so important to define your niche within the industry. By collaborating, we’re also collectively raising the standard of the industry.

As a community, WE have the final say in the trends that are out there. Why not define the standards as well? When we keep our secrets close, we aren’t contributing to the collective knowledge of the community. When we do share our secrets, however, we are holding ourselves and our peers to a higher standard — one that is defined by US, not an outside organization or voice. I don’t see a problem sharing my process for booking clients, if it means that another will become more efficient at it themselves. That being said, our processes are also very individualized. What works for me may not work for you, and vice versa; but sharing how I do it may inspire you to find a way that DOES work for you. With that comes a better reputation for client experience for both you and the industry as a whole, which benefits all of us. I already mentioned that collaborating and sharing secrets raises the collective standard of the community, but it also positions you as an expert! Both those in the industry and out of it (aka potential clients) will see you as an authority on the subject. I’m sure I don’t need to tell you why that’s a good thing. So don’t be afraid to share ideas or collaborate on a project with another planner. If anything it will only strengthen your own reputation and set of skills, which we should constantly striving for as it is.

Share

About the Author

Joelle Duff
Joelle Duff
Joelle Charming
Joelle Duff is the Creative Director of Joelle Charming, a wedding design boutique and lifestyle blog. After five years in the wedding industry, she has built a reputation for beautiful and luxurious weddings in the Santa Barbara area. She currently manages the Wedding Planner Collective, an online resource and community for both aspiring and professional wedding planners.
The website encountered an unexpected error. Try again later.
TypeError: Drupal\ap_gallery\Plugin\QueueWorker\GalleryJsonQueueProcessor::__construct(): Argument #6 ($file) must be of type Drupal\s3fs\S3fsFileService, Drupal\s3fs\S3fsFileSystemD103 given, called in /var/www/ap/web/modules/custom/ap_gallery/src/Plugin/QueueWorker/GalleryJsonQueueProcessor.php on line 63 in Drupal\ap_gallery\Plugin\QueueWorker\GalleryJsonQueueProcessor->__construct() (line 46 of modules/custom/ap_gallery/src/Plugin/QueueWorker/GalleryJsonQueueProcessor.php).
Drupal\ap_gallery\Plugin\QueueWorker\GalleryJsonQueueProcessor->__construct() (Line: 63)
Drupal\ap_gallery\Plugin\QueueWorker\GalleryJsonQueueProcessor::create() (Line: 21)
Drupal\Core\Plugin\Factory\ContainerFactory->createInstance() (Line: 83)
Drupal\Component\Plugin\PluginManagerBase->createInstance() (Line: 63)
Drupal\Core\Queue\QueueWorkerManager->createInstance() (Line: 208)
Drupal\Core\Cron->processQueues() (Line: 162)
Drupal\Core\Cron->run() (Line: 75)
Drupal\Core\ProxyClass\Cron->run() (Line: 65)
Drupal\automated_cron\EventSubscriber\AutomatedCron->onTerminate()
call_user_func() (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch() (Line: 115)
Symfony\Component\HttpKernel\HttpKernel->terminate() (Line: 66)
Drupal\Core\StackMiddleware\StackedHttpKernel->terminate() (Line: 715)
Drupal\Core\DrupalKernel->terminate() (Line: 22)