I recently talked with my good friend Denny Cherry (@mrdenny | blog) about my experience at the NoSQL Now! conference and working with NoSQL technologies. Denny’s new podcast series is called People Talking Tech and he has other interesting topics and people coming up soon.
My comments focused on how at the NoSQL professionals understand that it means "Not Only SQL" and can’t mean "No SQL" and have much of a future. Using the right tool for the right job. Cost, benefit, risk and all.
One of the things we talked about on the closing panel is "how do you find somebody that is a good architect who can tell you which types of technologies you can use for which use cases…"
Even though many people talk about NoSQL needing no architecture, we still need people to help choose when and what NoSQL technologies to use. Seems to me that having experience working hands-on with relational and NoSQL technologies is going to be hugely valuable in the next couple of years. If you have relational experience, now is the time to start learning about non-relational ones.
By the way, we talked a bit about database security. Denny’s new edition of his book Securing SQL Server, Second Edition: Protecting Your Database from Attackers has recently been released. Check it out.
I’ll be doing two sessions at SQL Saturday San Diego this weekend:
The first is with co-presenter, Tom LaRock (@sqlrockstar | blog), where we debate, whine (Tom) and win (me) several database design approaches and methods in front of a live audience (you!). This is a warm up for our PASS Summit spotlight presentation.
Database Design Throw Down
Karen and Tom debate about the options and best practices of common and advanced design issues, such as: * Natural vs. Surrogate keys * NULL vs NOT NULL * Datatypes * Agile Database Design * Database Refactoring * Identity Crisis ? …and others. Bring your votes, your debates, and your opinions. Help us figure out who’s right and who wrong…or less right.
Session Level: Intermediate
My second presentation is on career management.
Career Management for Data Professionals
Career Success in Data Management during Turbulent Times: A workshop on issues and ideas that today’s data professionals can do to build their careers and networking skills with other data management professionals. Workshop topics will include: • Demonstrating your expertise • Building a portfolio of your success stories • Getting others to sell your skills and business value • Building & extending your data management skill set • 10 Steps to highlighting you and your work Bring your thoughts, ideas, and experiences.
Session Level: Beginner
There are many great speakers at this event and it’s FREE for a full day of learning. Registration is still open, but it is common for these events to sell out before the event. Register now!
I’ll be returning to the DAMA Puget Sound (Seattle) group to give an advanced data modeling presentation on how to add more value and be more valued while you data model. This is a great group and I hope you can join us.
Advanced Data Modeling: Be Happier, Be More Valued and Add More Value
In this presentation, Karen will discuss the current state of data modeling and data architecture efforts and where we need to be in the current development and database environment to continue to provide value. Topics will include:
· If the modeler isn’t happy, the data isn’t happy
· Data Modeling in an Agile / SCRUM / modern development projects
· Big Data and other euphemisms
· NoSQL, not-only SQL non-relational, post-relational or whatever you want to call them
· Tools: Where are we, where do we need to be
· Being physical doesn’t mean you have to get dirty
· 10 Steps to happiness, being valuable and providing value
This presentation will be highly interactive, highly relevant and mostly irreverent. As usual.
Sr. Project Manager & Architect, InfoAdvisors
Karen Lopez is a Senior Project Manager and Architect for InfoAdvisors. A frequent speaker at conferences and local user groups, she has 20+ years of experience in project and data management on large, multi-project programs. Karen is a chronic volunteer, a SQL Server MVP, and an active advocate for WIT and Data Quality.
Karen’s presentations are known for their lively and interactive approach to learning. Her motto: I want you to Love Your Data!
This is an evening event and there is a fee to register. See the DAMA PS website for more information on registering.
I’m asked do these sorts of “make a recommendation for a solution” presentations all the time. I know how difficult it is. These presentations are different than teaching moments. They need to have a certain structure:
- Problem statement / Challenges
- Summary recommendation
- Detailed recommendation (with the whys, too.)
- Very brief recommendation of a path forward
So I have these tips for presenting your recommendations:
1. Make your material readable. It sounds so non-technical and trivial to say that fonts and diagrams matter, but they do. A recommendation that can’t be seen or read is less than useful. Every Be The Next Microsoft Employee contestant struggled with this, some to the point that we weren’t even sure what was being presented. Don’t let your presentation materials get in the way of presenting your ideas. Handouts of key diagrams are always beneficial. Using zoom features can help, too. Buck had a great tip: put your laptop on the floor, then stand 3 metres away (okay, he said 10 feet) and see what it looks like. If you can’t read it, neither can your audience. If you are presenting on older projectors or without a proper screen, then stand back 12 feet. If your slide looks like a blog post, you are doing it wrong. Concepts go on slides, not documentation.
2. Don’t make promises you can’t keep. All the contestants used words that could come back to haunt them later. Words like guarantee, promise, for certain and warranty are things you can’t commit to as a vendor or presenter. You don’t have the information you need to make these commitments, nor do you have any idea how your solution will be implemented. Instead of making promises, case studies and well-qualified data can back up some assertions, but you will still need to use many qualifying words like may, might, and can to ensure that you aren’t making promises you can’t keep.
3. Know why are you are recommending something. My mantra is every design decision comes down to cost, benefit and risk. There is no one right answer for every organization, environment, team, culture or financial situation. It’s not enough as an architect to say “this is the way that everyone does this”. A professional architect knows that solutions need to be implemented in the context of cost, benefit and risk, including legal and organizational constraints. Some people feel that costs and risks should not be addressed, but I have much more confidence in a recommendation when I can see that the recommender understands the trade-offs associated with everything they are proposing. If your recommendation includes legal constraints, confirm, verify and reconfirm your recommendation. Keeping your client out of jail is a good thing. Context is King…and Queen.
4. Ensure that you address all the parts of the problem. If a client asks you to solve their performance problem, all the solutions to address something else won’t make much of a difference if you don’t address the performance problem. They may also suspect that your proposed solution can’t solve the problem in any manner. Don’t forget the cost side, either. Be ready with multiple levels of solutions to meet the financial constraints of the audience.
5. Ensure you don’t try to solve a problem you weren’t asked to. I’ve seen this before: a consultant has solved some brilliant problems in the past and spends all his time talking about how his solution will solve that problem…but not that was totally out of scope of the request. Management may already have a solution in progress. One of our contestants threw in a last second proposal to replace an ERP system, something that wasn’t asked for at all. This would have been a real shock to everyone in the room and probably derailed the rest of the discussion. Stick to the scope of the problem.
6. Be confident & positive. Even if you aren’t. I mentioned that all our presenters showed signs of nervousness. That’s to be expected. But audiences really do want to see a confident speaker, one who speaks up and shows confidence in his or her solution. The best way to do this is to be prepared and be confident in what you are presenting based on the resources you were given. Don’t worry about the fact that you didn’t have enough time, that some things you wanted to demo you couldn’t get to work. You can’t change that. Go with what you have and do it well. Be strong.
If you are there to provide a solution then you should be showing the meeting group that you think what you are presenting is a good thing. Be serious, but even when you are talking about a problem or risk there’s no need to add drama to the situation. The current environment and situation might have serious problems, but there’s no need to be negative about that. In fact, I’ve seen consultants come in and mock the heck out of current situation and be totally oblivious that the people right in front of them built that solution and have done miracles trying to keep it going under changed demands.
7. Watch your time. Don’t end too early nor go long. Leave plenty of time for questions, comments and clarifications. You can have some backup materials for anticipated questions. I believe, though, the best use of time is for a discussion to ensure everyone understands what you have recommended and why.
8. Make your presentation about THEM. It’s so painful to see a presenter that is clearly presenting about THE PRESENTER. If you are saying I, my blog or my book too many times, you might be that guy. If you are constantly pointing to yourself, you aren’t focusing on the solution. If you are making a recommendation, it’s fine to say we recommend (if you are representing a group or organization), but you should be putting the client’s needs at the forefront. Not yours. One of the best ways to show that you are about them is to start your presentation with a brief understanding of the problem and the pain points of the organization. Don’t spend too much time on it, just reflect what you’ve been told and show along the way how your recommendation addresses their pain points.
Recommendations need to have have the what, why, and how much questions addressed. They need to be clear and understandable. I’d love to hear what recommendations you have for making technical recommendation presentations.
On Thursday, 2 August I’ll be debating with Tom LaRock (@sqlrockstar), giving a preview of our SQL Saturday presentation of Database Design Throwdown: The Trailer. In this wonderful smackdown, I’ll be talking about the importance of data quality, integrity and data governance while preparing database designs. I’m pretty sure Tom will be spouting wildly crazy, kooky ideas about performance, optimizing design to make life easier for DBAs and … I have no idea what else. Probably bacon. We won’t be giving the same presentation as on Saturday — it will be more of a trailer version of that. Oh, wait…that doesn’t quite sound right. It will be a teaser. Yeah. Something like that. A teaser.
Kansas City SQL Server User Group
Details about the SQL Server User Group meeting:
- 3:45 – 3:50 Greeting and Housekeeping
- 3:50 – 5:00 Database Design Throwdown: The Trailer
- 5:00 – 5:15 Door prizes and wrap up
Overview: If a man is alone in the forest and there is no woman around to watch him design a database is he still wrong? Join us in this highly interactive debate regarding the options and best practices of common and advanced design issues such as natural versus surrogate keys, NULL versus NOT NULL, data quality versus performance, and others. Bring your opinions and experience and join the discussion.
Thomas LaRock is a seasoned IT professional with over a decade of technical and management experience. Currently serving as a senior database administrator with Confio Software, Thomas has progressed through several roles including programmer, analyst, and DBA. Prior to that, he worked at several software and consulting companies, working at customer sites in the United States and abroad. Thomas holds a MS degree in Mathematics from Washington State University and is a member of the Usability Professional’s Association. Thomas also currently serves on the Board of Directors for the Professional Association for SQL Server (PASS), is a SQL Server MVP, and can also be found blogging at http://thomaslarock.com and is the author of DBA Survivor: Become a Rock Star DBA (http://dbasurvivor.com).
Karen Lopez is Sr. Project Manager and Architect at InfoAdvisors, Inc. Karen is a frequent speaker at conferences and user groups. She has 20+ years of experience in project and data management on large, multi-project programs. Karen specializes in the practical application of data management principles. Karen is also the ListMistress and moderator of the InfoAdvisors Discussion Groups at www.infoadvisors.com.
8700 State Line Road
Leawood, KS 66206 (map)
Data Model Driven Database Design
On Saturday, 4 August I will be presenting at the Kansas City SQL Saturday (aka #SQLSat159 — don’t get me started on why they use a surrogate key as their names for these…) on Model Driven Database Design
Model-Driven Database Design
Model-Driven Database Development: Myths, Magic and Methods. In this presentation, Karen discusses data model-driven database development from the point of view of the Data Architect, the DBA, and the Developer. She will cover topics such as "Who does what?", "Why are we doing this?", "Do I have to Use a GUI?" and "Just who do you think you are?". Demos, too. Finally, 10 tips for making model-driven database development successful in your organization’s culture and environment.
Session Level: Beginner
Location: Cerner Corporation’s Riverport Campus, 6711 NE Birmingham Rd, Kansas City, MO, 64117
And Tom and I will be doing our full debate on Database Design: The Throwdown, as described above. Registration is required for the SQL Saturday, but it’s totally free – you get swag, prizes and access to some of the best speakers in the SQL Server community. I attended this last year in Kansas City and they did a fabulous job. You want to be there, too.
As I shared with you previously, I’m a guest judge on Microsoft Learning’s new reality show, Be The Next Microsoft Employee. In this contest, four SQL Server DBAs compete for a chance to work at Microsoft. They have to go through all the normal Microsoft interview processes PLUS compete in front of cameras, crew and the Internet on a series of data-related challenges. The challenge I participated in, filmed on the Microsoft campus, was the last one and it was a doozy.
It should be no surprise to you that I took the Technical Barbies (@Data_Model and @VenusBarbie) along for the filming. Since this was a hiring contest, I also brought along Working Woman Barbie, who comes with a suit that also turns into a glittery dance dress for after work fun. Working Woman Barbie can talk, too. She says fun things, but she talks too much about Ken.
When we arrived at the shoot, the first thing the Barbies got was a professional makeover. Stylist Mimi Pettibone of StellarStyle.com has previous professional experience styling Barbies and action figures. HOW LUCKY WAS THAT? Mimi also gave me some great tips about styling and posing the Barbies. Fishing line seems to be a key component. I also showed her how I used clear braid rubber bands to help keep Barbie from losing her cell phone and shoes. Just like I do. Or should.
I live by a man’s code, designed to fit a man’s world, yet at the same time I never forget that a woman’s first job is to choose the right shade of lipstick.
- Carole Lombard
I’m not sure I agree with Ms. Lombard there, but both the Barbies and I had to wear lipstick for this shoot. That’s how I knew I was on a reality show…just a different type of reality.
We took some before and after pictures. I think I pretty much looked the same as VenusBarbie. Mimi worked wonders with me.
Mimi did a fabulous job, don’t you think?
Subscribe via E-mail
- Karen Lopez on Strutting: We all Know When You are Doing It. So Stop.
- Joey D'Antoni on Strutting: We all Know When You are Doing It. So Stop.
- Karen Lopez on Strutting: We all Know When You are Doing It. So Stop.
- Thomas LaRock on Strutting: We all Know When You are Doing It. So Stop.
- Karen Lopez on Strutting: We all Know When You are Doing It. So Stop.
- May 2013 (4)
- April 2013 (5)
- March 2013 (4)
- February 2013 (7)
- January 2013 (12)
- December 2012 (2)
- November 2012 (3)
- October 2012 (3)
- September 2012 (13)
- August 2012 (5)
- July 2012 (17)
- June 2012 (2)
- May 2012 (4)
- April 2012 (4)
- March 2012 (8)
- February 2012 (11)
- January 2012 (3)
- December 2011 (10)
- November 2011 (8)
- October 2011 (5)
- September 2011 (3)
- August 2011 (9)
- July 2011 (5)
- June 2011 (5)
- May 2011 (5)
- April 2011 (9)
- March 2011 (4)
- February 2011 (9)
- January 2011 (8)
- December 2010 (15)
- November 2010 (27)
- September 2010 (2)
- August 2010 (1)
- July 2010 (4)