Philly New Tech Meetup -- CIO Panel

Wednesday, May 16, 2018
5:45 PM 7:45 PM 17:45 19:45

Quorum at the Science Center 3711L Market Street Philadelphia, PA, 19104 United States (map)

Google Calendar ICS

This month we'll be chatting with local corporate CIOs and technology Vice Presidents about what new technologies they're keeping their eyes on. We'll also be talking "Entrepreneurial Thinking in Corporate Tech".

More information coming soon!

5:45 Networking and food

6:15 Welcome and sponsors

6:20 CIO Panel

Sandeep C. Katarnavre
Chief Information Officer & VP, IT.
Saint Gobain Construction Products North America
https://www.saint-gobain-northamerica.com/business/brands/certainteed

Vipul Chokshi
VP of Information Technology
C&D Technologies [https://www.cdtechno.com]

Mark Wheeler
Interim CIO
City of Philadelphia

Karen Stine
VP, Enterprise Information Management
The Radian Group http://www.radian.biz/page?name=AboutUs

MODERATED BY:
Eloise Young
SVP Strategic Planning & Information Services
Philadelphia Gas Works (PGW)

6:40 CIO Q&A

7:20 Community discussion followed by Networking

7:45 Happy Hour

Source:: https://www.meetup.com/Philly-New-Tech-Meetup/events/249340713/

Growth Strategies, Leadership

If Everyone Is Playing Defense with their Goals, Nobody Is Trying to Win

Ask a room of leaders why they set goals and most will say accountability. That answer creates the problem. Goals exist for alignment. The company needs to reach a number, so this group does this, that group does that, and together the math works. Everyone is pointed in the same direction. Focus comes second. A good goal tells you what to say no to.

Leadership, Organizational Dev

If Ten People on Your Team Agree, Nine of Them Are Unnecessary

The instinct to build a team that moved in the same direction, at the same pace, with the same set of perspectives is limiting. Consistency is created at the expense of range. The goal isn't alignment of strengths. It's coverage. The most dangerous teams I've seen weren't the ones with conflict. hey were the ones with none. Where every conversation ends in agreement. Where nothing gets surfaced. Where the people who see things differently may have learned to stop saying so.

Leadership

Shiny Object Syndrome Will Break Your Company. It's Also What Built It.

The same restlessness that makes it hard to stay on plan is what made them start the company in the first place. The wandering mind, the refusal to be satisfied with what already exists, the ability to see something before it exists: that's not a disorder. That's the source.

The Bridge to the Moon

If you're building a company, knowing your role isn't optional. The visionary needs someone who will build what they see without getting in the way of the seeing. The integrator needs someone who will point at the moon and mean it and keep pointing at the same moon long enough for the bridge to get built. The mistake I see most often: trying to be both or hiring someone who mirrors you when you need someone who complements you.

The Problems You Haven't Earned Yet

The fear of success doesn't usually announce itself as fear. It sounds like planning. It sounds like due diligence. It sounds like being responsible.

What it actually is: A limiting belief. It’s spending today's energy on problems you'll only face if you win

Organizational Dev

Right Person. Promoted to the Wrong Seat.

Right people, right seats doesn't mean everyone eventually moves into a leadership role. It means finding the seat where each person does their best work and building a structure that makes those seats worth staying in. Create a path for people who want to grow as individual contributors. Create a separate path for people who want to lead. Reward both. Respect both. Pay both.

Scraped Knees and Bus Crashes

Don't prevent scraped knees; prevent bus crashes. A scraped knee hurts. You might carry the scar for years. That's the point. The pain is proportional to the lesson. A bus crash can lead to catastrophic loss. The project. The company. The relationship. Something that can't be recovered. The leader's job isn't to eliminate mistakes. It's to know the difference between those two things.

Organizational Dev, Leadership

What Leadership Teams Learn When the Helicopter Goes Down

The leader's job isn't to have the answer. It's to create conditions where the best answer can emerge. That means encouraging disagreement without punishment. Creating opportunities for information to move across functions. Making it safe for people to challenge assumptions, including your own. The highest-performing teams in these simulations don't succeed because they have the smartest leader. They succeed because nobody in the room is waiting for one person to have all the answers.

Calendar

Events

Philly New Tech Meetup -- CIO Panel

Trajectify