![]() |
Group Portrait: A Wedding Celebration, by Gillis van Tilborgh (Metropolitan Museum of Art) |
By 50, a man should have played a role in a few weddings, and I've been involved in my share. I've hosted two, one for my brother at my apartment on Logan Blvd., one for a pair of readers at the Willis Tower Skydeck. I've been a best man and a groomsman and helped throw a surprise bachelor party at a bar in New York City. Not to mention the many weddings I've attended as a guest, including one atop the Ferris wheel at Navy Pier and, of course, my own gilded affair in the Babylonian splendor of the Hotel Intercontinental in downtown Chicago.
My involvement in these weddings has left me with one central piece of wedding wisdom that I impart to all prospective brides — something those brides-to-be whose wedding dresses went up in flames Wednesday at Eva's Bridals of Oak Lawn learned big-time, but which holds true for every wedding and deserves being stated whenever possible:
Something always goes wrong.
Always, always, always.
Oh, I suppose the most casual affair — a quick exchange of vows in the Cook County Clerk's office — can go off without a hitch. But anything more complex than that — plan to open a jar of nuts and beat a tambourine afterward — and the possibilities for screw-ups swiftly multiply.
This of course is completely opposite to the standard bride's goal of a "perfect" wedding, whatever her idea of perfect might be, from arriving in Cinderella's glass carriage in a cloud of doves at a ceremony officiated by Mickey Mouse, to standing barefoot behind the counter at the McDonald's where you met your beau.
These brides operate under the false impression that just because they've planned something for months and paid an ungodly sum of money for it, therefore they can expect everything to come off without a hitch.
That's not how life works
At our wedding, I wasn't hoping for perfect — guys seldom do. A guy, if he's marrying the right person, will be happy if his bride shows up. I was content to let my bride plan the wedding of her dreams, limiting my participation to a few symbolic contributions which consisted, if I recall, of a) putting carrot soup on the menu. (I like carrot soup) and b) insisting that, if we were going to have a band, it had to be a good band.
Carrot soup is easy. And a good band is attainable, if you spend enough. But "perfect" is another matter entirely. "Perfect" is generally synonymous with "impossible." Oh, you can bowl 300 or pitch a perfect game, but with something as complex as a wedding, with the flowers and the chapel and the reception and the music and the meal and the guests, the odds of it all coming off perfectly are scant.
Expecting wedding perfection is a recipe for disaster because there are so many things that can go wrong. A colleague and his wife asked for their wedding cake to be "creme" and it showed up "green" -- say the words out loud. A wedding cake with mint green icing.
They laughed — which is key. The secret to a perfect wedding is not guaranteeing that everything unfolds perfectly — it won't — but in ignoring or shrugging off imperfections.
I was immensely proud that my bride, when she opened the box from the florist containing her bouquet, calmly noted that it was not the round bouquet she ordered, but a draped nosegay. Some brides would have lost it at this point, but she observed that they were still beautiful flowers and it was too late to do anything. An even-keeled acceptance that probably explains how she could marry me in the first place, and that has served us well, lo these past 20 years.
You can plan for perfect. You may think of your wedding as a stage play — you may write a script, plan various entrances and exits.
But once it is happening, you must abruptly shift, abandoning the stage play paradigm, jettisoning hopes of "perfect," and view it as a party. You know how parties work — you plan, then let the thing unfold.
That way, if something happens that's not in the script — your aged uncle stands up in the middle of the vows and begins a rambling toast, or your wedding dress is burned up in a fire — you adapt. The uncle is coaxed to his seat; another wedding dress is found elsewhere. It immediately becomes a good story.
Weddings are luxuries, but useful luxuries — they can give a couple a good running start up the hill of married life. Sure, you can stamp your foot and insist on perfection. Good luck; maybe that'll work for you. But it's easier if you expect something will veer off course, look for it, wait for it, and when it occurs, say, "Right, this is the thing that's going to go wrong at my wedding."
My wife and I, to this day, sometimes warm ourselves on the still-glowing embers of our wedding. Not because it was perfect, but because when glitches happened, we hopped over them and kept going. It didn't unfold perfectly, but it's perfect now.
— Originally published in the Sun-Times, Nov. 29, 2010
I hope it's a great wedding & your new daughter-in-law isn't a bridezilla. ;s
ReplyDeleteAnd Neil, it will always be Sears Tower, not out of any love for Sears, but they did pay cash to build it, no mortgage, & the the sole reason for the name change is that creep Richie Daley paid the Willis Company $15 million to move their US offices to the building & then Willis paid Vornado, the new owner of the tower $15 million for naming rights.
So in reality, we the taxpayers of Chicago should get to name it.
And the Chrysler Building in NYC has been sold about five times since Walter Chrysler died in the mid 1950s, but not one of the owners ever even thought of changing the name!
All brides are lovely, and we mustn't forget this.
DeletePreach :)
DeleteI would love to hear all the saga after the wedding is done. My daughter’s wedding had plenty of glitches but among the most crazy: the wedding planner of my daughter’s Orthodox wedding ceremony ( we are not Orthodox….the only person who was? ….the rabbi! Long story) forgot the kippahs and then lost the Ketubah after the ceremony.
ReplyDeleteA blessing upon your family and your son and his wife!
ReplyDeletewell said! May your entire family enjoy the day.
ReplyDeleteGained so much weight before my first wedding, thanks to meds I was taking, that my clothes didn't fit. In the photos, I looked like a fat pig. Wasn't happy. We were old enough to know better, but we wrote our own ceremony (she was Lutheran, I was Jewish), with the help of the Unitarian minister who officiated (hey, it was the Eighties). Truth was, we'd been legally married (at City Hall) a month earlier.
ReplyDeleteDon't remember anything we said, but I will never forget that the outdoor ceremony actually included the word "inasmuch" in the text. And goblets of white wine were involved. As I was lifting mine, a large buzzing insect (possibly a bee) flew into the glass, landed in the wine, and drowned in it. I had to spill the wine onto the ground and pretend that nothing was happening, while trying not to lose my cool.
Other than that, and neither my parents nor my sister showing up, everything went pretty much according to plan. It was our day, our ceremony, our venue, our menu, our cake, our guest list, our friends, and my wife's family. We called all the shots, and we footed the bill. It all went down smoothly. At least, that's how I remember it...37 years later.
The second marriage included my obnoxious father getting in people's faces, my young niece messing up our house, and a fender-bender outside in the snow. But I'll skip all that for now. Could have been worse. The day my best friend was married was also the day that RFK was buried. Everyone donned their game face, and soldiered on.
Congratulations. Best wishes for your son and his partner, may their marriage be as fortunate as yours.
ReplyDeleteMazel Tov, Neil! I was a guest at that surprise bachelor party (I think you’re talking about REL’s). Thst was a great party you threw! (And, obviously, the only bachelor party I have ever attended or ever will.) This is Gayle. So happy for your whole family.
ReplyDelete