Pages

Follow Me on Twitter

Showing posts with label agile. Show all posts
Showing posts with label agile. Show all posts

Tuesday, June 4, 2013

Secret of Successful Families: The Family Meeting


Bruce Feiler sums up his research on happy families by offering a “nonlist list of things that happy families do.” This list consists of the following three nonrule rules:
  1. Adapt all the time. 
  2. Talk. A lot. 
  3. Go Out and Play.

Feiler offers multitudes of ways to follow each of these nonrules. One of them is the family meeting. The family meeting appeals to me for several reasons.


  • First of all, there is so much in a minute. You don’t even have to have relatives who are psychoanalysts to know this. Nor do you have to be a mindfulness meditation expert. Just think about how (surprisingly) much it hurts if a driver passes you and gives you the finger, for example. And that’s someone you don’t even know, and a situation that’s not even personal. Now think about all the casual remarks that pass among family members rushing around to ballet and soccer and work that affect you. A stray snap on a day when you have a short fuse can have its own sort of a butterfly effect on your mood and life. Yes, it’s true, I do have relatives who are psychoanalysts, AND I practice mindfulness meditation, so I may be a bit more invested in what’s going on under the surface in a moment than most. In fact, this may be the secret to my failure more than anything else – all that time parsing and analyzing can get you into a thoroughly tangled state of conflict and make it hard to move forward with your goals. But since that last sentence completely undermines what I’m getting at, let’s pretend that I’m 100% in favor of trying to understand your emotions in a situation, so that you can make an informed decision, or can react intentionally instead of instinctively. This takes time, and conversation. A meeting provides a forum to catch some of those moments that could use a little dissecting: To address some of those moments that result in decisions on the fly – decisions and their effects that never get fully explained.


  • Second of all, a family meeting sounds like a reasonable idea when it’s hard to find regular nights to eat together because this one’s got an extra rehearsal and that one’s soccer game time changed and that one forgot he had to teach his medical students and the other one has a book club, because all of those ones have book clubs; you’re not actually a suburban mommy if you don’t - but that’s another story. These meetings don’t have to be long. They shouldn’t be long. Sunday night, which Bruce uses, seems like a good time to me. Usually everyone is home then, and there’s an opportunity to look at the calendar. This doesn’t guarantee that we won’t be scrambling for forgotten appointments, but it does help us become aware of our commitments, at least for a moment, together. This group moment might well improve the chances that we’ll get where we need to be on time. I make no promises, nor do I have any proof, since as of this writing, our family has had only one family meeting.


  • Third of all, the family meeting, as Bruce describes it, is child-centered. Or to be more precise, while parents may set the agenda, the children should be vocal participants. This gives them practice explaining themselves, exploring and expressing their opinions, and listening to others’, which I defy anyone to deny is good life training. Since the message in my family of origin was “Children should be seen and not heard,” this idea appeals to my rebellious inner child. Let the children be heard and seen. Then let the parents make final decisions.


  • And last of all, the family meeting is a way to solidify or otherwise emphasize the idea of the family unit as a unit. I like this idea of emphasizing the family as a unit. It’s one of Bruce’s ideas that’s so fundamental you don’t even see it: To be a successful family involves focusing on the family itself, and seeing it as a working group, not just as a staging ground for “real life.”

The Meeting

Now, I’d been mulling this idea for a while. I was intrigued and wanted to do it, despite the hoke factor. So when the 5th grader came home, I think it was the very day I behaved so admirably at the DARE assembly, with a letter announcing that she’d won a leadership award, and that there would be a ceremony at an arena at a community college to recognize her and the other recipients, I had my entrĂ©e.

Readers, if you would kindly lower your bayonets, I will continue. After feeling my moment of pride in my offspring – a moment immediately followed by one of complete amazement: I have never won thing one for leadership – I realized that this ceremony would conflict with the 9th grader’s ballet schedule. Frankly, that went without saying, since the 9th grader spends less time not dancing than she does dancing. So the question was, should she miss the classes, which were in rehearsals for her end of the year performance, to attend her sister’s ceremony? Perfect for a family meeting.

I’d like to tell you that each participant met the announcement with equal enthusiasm; but that would be a lie. The husband was on board – surprising to me, considering the aforementioned hoke factor.  He was even willing to commit to weekly meetings. However, when we told the children we were having a meeting,  the 9th grader’s reaction was, “Oh no,” and the 5th grader’s was, “Are we in trouble?”

But it went well. Or at least, it didn’t go badly. When I brought up the awards ceremony - ballet schedule conflict, I tried to remember Bruce’s advice to let the children do a lot of the talking. The 5th grader immediately announced that she wanted her sister to attend her award ceremony. The 9th grader countered immediately with acquiescence. Conflict resolved? More like conflict swept underground. I suddenly saw how good an idea a family meeting was. I think it’s the kind of thing that might just help keep people close. If you’re the kind of person who acquiesces because your sister states a strong preference, despite your own mixed feelings, then eventually, you may avoid your sister, to avoid hearing her state her preferences. But if your sister can start to understand that her preference acts like a command, then she may begin to be a little more careful and less categorical – more empathetic – in stating it.

Since their conversation had apparently ended, it was up to me and the husband to stir the pot. How did the 9th grader feel about missing the ballet class to go to the ceremony? For that matter, how would the 9th grader feel about having her sister at her upcoming recital? And how would the 5th grader feel about the looming conflict over missing a soccer tournament to go to (another) dance recital? I wanted the conversation to be both concrete (about this particular conflict) and hypothetical (attending each others’ awards and recitals, etc.) Okay, I know, this may be slightly nauseating, as if I envision a golden-paved road of award upon award for my children, stretching into the future. However, even the most curmudgenly reader must admit there are many milestones ahead (God willing), with attendant ceremonies. It seems worthwhile to figure out who needs to go to what when.  But mostly, I wanted the big sister to express her preferences and feelings about attending her sister’s award ceremony, and to see how important her presence was to her younger sister. Also, I wanted the little sister to realize that her big sister would be sacrificing something very important to her (dance class) at a difficult time (rehearsing for upcoming recital).

The upshot was that we, the parental units, listened to the children, and then we told them we would make a decision. Meeting adjourned. Not exactly an unqualified success, but not terrible, either. Later, the 9th grader came to us privately and said she didn’t want to miss her class. We told her we had wanted her to say that at the meeting so that the 5th grader would know, but of course she hadn’t wanted to hurt her sister’s feelings. I suppose immediate openness was too much to expect from one meeting.

In the end, we decided the 9th grader should go to the ceremony. In private, I told the 5th grader that her sister was making a sacrifice by missing her rehearsal. The 5th grader said, “Now you are making me feel guilty.” I told her I wasn’t trying to make her feel guilty as much as I was trying to make her appreciate that her sister was doing something nice for her – and that she ought to thank her.

So the 9th grader came to the ceremony. On the way, the 5th grader thanked her for missing rehearsal. Afterwards, the 9th grader hugged the 5th grader.

Overall, I thought it was good for the 9th grader to hear her sister characterized as a leader, and good for the 5th grader to know her sister heard that characterization.

We haven’t had a family meeting since; but I stand by the process.



Thursday, April 25, 2013

Agility isn't Just for Physical Phitness Anymore



Okay, there’s a book I’ve been avoiding: The Secrets of Happy Families, by Bruce Feiler. It’s bright and yellow and friendly looking, and it’s been sitting on my shelf for a few months, but I’ve avoided it. You have to admit – or at least, I have to admit – the title is a little threatening. Sure, it’s catchy, and there’s that reference to Anna Karenina implied in it, but the thing is, my family is on the old side. The 9th grader is, well, in 9th grade, and the 5th grader is also no longer a small child. As for the partnership slash marriage slash union between the husband and me, that’s also in its teens. It’s not like we’re newlyweds, or just starting the kid process. What if everything we’ve been doing so far is, you know, wrong? 

Even scarier is the question that follows a book with that title, like night follows day and yin follows yang: What if I learn those secrets of happy families, and discover that our family doesn’t know them? What if my family isn’t happy?

I mean, is it? I mean, I think, objectively speaking, we’re a happy family. Or happy-ish. Within the bounds of love, we like one another. We laugh – and not only at one another. There’s some yelling and some pouting and some crying. That’s normal.

Right?

I’ll admit, I read a column Feiler wrote a couple of weeks ago that gave a little glimpse into the book. The column was about fighting well. Or, perhaps I should say, about resolving conflicts. There was a nifty bit about how if you need to have a difficult conversation with someone you should make sure everyone is sitting at the same level. Don’t have someone on a footstool and someone on a counter stool. The butts should be on the same level. Level playing field, so to speak.

There was another nifty bit about making sure, when discussing topics of potential conflict, such as curfew violations or other infractions, that you sit side by side with your child, because that position encourages collaboration and minimizes the confrontational aspect of your, uh, confrontation. Here, butts should rest on cushions, because flexibility under the butt contributes to flexibility in the head.

Very interesting.

What’s so threatening about that stuff, you wonder? Well, I’ll tell you.
Readers, there is always a chance that everything I have ever done as a mother, adult, person, embryo, and zygote has been a mistake. So I read that piece, and I thought, geez, we haven’t had many fights and arguments with the children. We’re not a big fighting arguing punishing family.

Is that wrong?

Maybe the children are just not old enough for that kind of problem and it’s comin’ down the pike. If so, I have now made note of all cushioned seating in the house and will be sure to use it. Maybe, though, something in our parenting style has squelched the children. I have enough amateur psychological knowledge to know that feelings is feelings and they don’t just vanish. Perhaps our style, the husband’s and mine, the rule-with-the-invisible-fear-of-invoking-our -displeasure style, which has so far SEEMED to serve us well, has created a system of stealth rebellion in the children. Maybe we have forced them to stuff their negative emotions. Maybe they are slowly simmering cauldrons of resentment, the kind that never boil over. Maybe this style will in turn drive them away from us and send them to the far pillars of the world, from which they will only return periodically, armed with spouses or partners, and never for more than three nights.

So I had a little fear about reading the book. Plus, a quick glance at other books Feiler has published revealed they skew religious. At least their titles do. Walking the Bible, Abraham, and Where God Was Born, for example. Which. Well, I’m wary of yet another book (or person) telling me I need to have some particular religious faith to flourish.  Also, a quick check of my search engine revealed that he’s already had four nonfiction bestsellers, has done a TED talk, has suffered from cancer, and is seven months younger than me, to the day. To top it all off, he has worked as a clown.

Despite these fears, aversions, skepticisms, and – let’s call ‘em what they are – jealousies, however, I cracked the book last night.

Not being at all competitive in any way - not that there’s anything wrong with being competitive, I have plenty of friends and relations who are competitive, it’s just that I am way above petty competitiveness - I wasn’t at all pleased to discover that the concept Bruce introduces in his first chapter, Agile development, is one I’ve learned already from my editing work on technology articles for a web content management company.

I’m calling him Bruce, now, because his book’s cover is after all so friendly yellow, and because it makes me feel more equal to him. Not that being equal matters. (See above, re: competitiveness.) Also, I was being ironic in that last paragraph, in case you weren’t reading with full attention to detail.

Anyhoo, yes, me and technology go way back. Back to high school, in fact; back to the Daisy wheel computer we had, with the password I just might have leaked to someone (a boy) at another school, thus causing an early hacking scandal.  I was never blamed for this, because apparently, someone else had also leaked the password to someone (a boy) at another school. She got caught, and I didn’t. So, my feelings of competence with technology were encouraged.

It occurs to me that this example is really something totally different than competence with technology. More like competence at lying low, a skill I honed, and which came in useful later in an episode involving several people (a boy) and Great Falls, Virginia, and some illegal substances. Which I actually hadn’t used, but I was there, it is true.

But I digress. I was trying to get to the story of how yesterday the 9th grader asked me how I would explain what a computer was to someone who had never heard of one. I asked her, “How would you explain it?” but she was having none of that kind of parent-answer that really turns the onus back on the questioner. So off I went on a ramble about code and ones and zeros, and was filled with fond remembrances of how I used to hang around with lots of MIT grads and how they could explain it to the 9th grader much better than I. But we got through it, somehow.

Anyway, Agile is a methodology, adopted from software developers, as an alternative to a traditional management approach to project development. Agile is based on a team model with lots of feedback and revisions at each step of the development process. It’s catching on in all kinds of enterprises, and it’s been quietly making a mark on family life. Says Bruce, “The core idea of agile development is that life is constantly changing, and we have to organize ourselves in ways to allow us to react to changes in real time. The centerpiece of the program is a weekly review session built on the principle of ‘inspect and adapt.’”  Thus, Bruce discusses establishing a weekly family meeting with a regular agenda of answering the following three questions: 1. What went well in the family that week 2. What things could be improved in the family? And 3., What will the family commit to in the next week?  The main benefit of the family meeting is that it provides a consistent slot for communication.

There are lots of other details, but this post is getting too long. And there’s a friendly yellow-covered book to read if you want to know more. It’s only one of Bruce’s many ideas, and it’s pretty interesting.  Not at all scary. I’m going to read on.