J.D. Meier's Blog

Software Engineering, Project Management, and Effectiveness

  • J.D. Meier's Blog

    Adam Grocholski on Timeboxing


    Adam Grocholski has a great post on timeboxing.  In his post, he shares his secrets of how he’s applied Getting Results the Agile Way to take control of his time.  One of my favorite parts is where he explains how he made a business case with his customers to spend less time in meetings, and more time producing results.

    Check out Adam’s post on Timeboxing.

  • J.D. Meier's Blog

    MSDN Library Home Adds Quick Links


    Jeff Braaten let me know that the MSDN Library Home is now featuring Quick Links … and it’s poetry in motion:


    The point behind the Quick Links is to help you jump quickly to some of the most popular areas of the MSDN Library.

    App Types / Platform Technology Clusters
    The links are clustered around key application types and platform technology areas:

    • Cloud Development
    • Data Development
    • Desktop Development
    • Game Development
    • Phone Development
    • Web Development

    API Reference, Code Samples, and How Tos by Technology
    At a glance, you can quickly jump to API references, Code Samples, and How Tos for some of your favorite technologies:

    • ADO.NET
    • ADO.NET Entity Framework
    • ASP.NET
    • Azure Tools for Microsoft Visual Studio
    • CSS
    • HTML
    • Internet Explorer
    • JavaScript
    • LINQ
    • Silverlight (out-of-Browser Support)
    • Silverlight for Windows Phone
    • SQL Azure
    • SQL Server
    • WCF
    • WCF Data Services
    • WCF RIA Services
    • Windows Client
    • Windows Phone Developer Tools
    • WPF
    • XNA

    Enjoy browsing the Quick Links!

  • J.D. Meier's Blog

    How Microsoft IT Does Cloud Computing


    While researching some cloud topics, I came across a nice resource on TechNet called How Microsoft IT Does It.

    It’s an insider’s look showcasing how our Microsoft IT department plans for, deploys, and manages our enterprise solutions across the business lines using our Microsoft product and technology platforms.

    Here is a roundup of the cloud-focused resources.




  • J.D. Meier's Blog

    Six Steps for Enterprise Architecture as Strategy


    One of my new favorite books is, Enterprise Architecture as Strategy, by Jeanee W. Ross, Peter Weill, and David C. Robertson.  My colleague, Danny Cohen recommended it as one of the best books on enterprise strategy and I agree.

    A big focus of the book is on execution and how to build a strong foundation for execution.  The key is an effective enterprise architecture.  With an effective enterprise architecture, you can improve business agility, achieve higher profitability, reduce time to market, lower IT costs, improve access to shared customer data, lower the risk of mission-critical systems failures.  Enterprise architecture as strategy means your enterprise architecture is addressing two key challenges: 1) integration and 2) standardization across the company.

    Six Steps to Build a Foundation for Execution
    Here are six steps Ross, Weill, and Robertson identify for re-thinking a foundation for execution and creating and effective enterprise architecture:

    • Step 1 –Analyze your existing foundation for execution.
    • Step 2 – Define your operating model.
    • Step 3 – Design your enterprise architecture.
    • Step 4 – Set priorities.
    • Step 5 – Design and implement an IT engagement model.
    • Step 6 – Exploit your foundation for execution for growth.

    Summary Table and Notes
    In this table, I  summarized key notes along with each step:

    Step Notes
    Step 1 - Analyze your existing foundation for execution
    • Identify digitized processes.
    • Figure out which processes are mission critical transactions.
    • Identify elements of IT that are world-class.
    • Evaluate the reach, security, data access, and flexibility you need.
    • Identify the strengths and weaknesses in your foundation.
    Step 2 - Define your operating model
    • Identify the processes that differentiate you competitively
    • Envision your ideal customer experience.
    • Determine how you want to grow (acquire or grow related businesses, expand globally, acquire competitors, offer more products and services.)
    Step 3 - Design your enterprise architecture.
    • Map out the essence of your business – your foundation for execution (companywide business processes, shared data, key technologies, and critical customer interfaces.)
    Step 4 - Set priorities.
    • Highlight priorities on the core architecture diagram (the base that the future capabilities depend on)
    • Align the project portfolio to match the enterprise architecture
    Step 5 - Design and implement an IT engagement model.
    • Create a formal IT engagement model (1) IT governance at senior levels, 2) disciplined project management across all major projects, 3) linkages that ensure IT governance and project management reinforce each other.
    Step 6- Exploit your foundation for execution for growth.
    • Plan to cash in on the benefits.
    • Allocate generous funding for training and development.
    • Align incentives so people are motivated to exploit the foundation.
    • Encourage and reward creativity.
  • J.D. Meier's Blog

    Reference Models, Reference Architectures, and Reference Implementations


    "All models are wrong, but some are useful." -- George Box

    I often see confusion over reference models, reference architectures, and reference implementations.  In this post, I’ll share my experience and learnings and observations:

    • Reference Model - A Reference model is a model of something that embodies the basic goals or ideas, and you can use it at as a reference for various purposes.  It’s like holding up a diamond and looking at the different facets.  It basically serves as a backdrop or canvas, or a foundation and springboard for deeper dives.  They are also useful for pulling together a bird’s-eye view of a domain or problem space.  A well-known example is the OSI model.  Key Attributes include: abstract, entities and Relationships, technology agnostic, and they clarify things within a context.  By using a model, you can focus on higher-level concepts, ideas, and decisions.
    • Reference Architecture - A reference architecture provides a proven template solution for an architecture for a particular domain.  It’s the high-level “blue prints” for putting the pieces of the puzzle together.
    • Reference Implementation - A reference Implementation goes beyond a reference architecture and is an actual implementation.  This is where the rubber meets the road and it serves as an exemplar down at the implementation level.

    I think the confusion is usually because the argument usually hinges on whether a reference architecture or reference implementation needs to be in code, when that’s really just a form factor decision.  The distinction is actually the focus and concern, independent of how you share it, although code can help illuminate a reference implementation and a reference architecture.  The other confusion is often around how big or small it needs to be to determine whether it’s a reference architecture or reference implementation, but that’ also a herring.  Again, it goes back to what the focus of the example is.  If it’s an exemplar of the architecture, it’s a reference architecture.  If it’s an exemplar of the implementation, then it’s a reference implementation, and each serve different purposes, and require different levels of detail or abstraction.

    Reference Model Examples
    Reference models give us a quick way to see and talk about a given problem space.  Here is an example of a simple reference model that does nothing more than frame out some cornerstone concepts for cloud computing.  In this case, it’s a visual model for cloud computing:


    This is another of my favorite reference models.  In this case, this is a continuum of moving up the stack with types of cloud services from IaaS to PaaS to SaaS :


    I also like a few of the cloud reference models, especially how they can be used for overlaying security concerns.

    Reference Architecture Examples
    The beauty of the reference architecture is that you can shape the application before you implement it.  One of the simplest ways to achieve this is to whiteboard it.  When you put it on the whiteboard, you can focus on key engineering decisions and avoid getting lost in the details.  You can focus on a conceptual, physical, or logical view, … you can focus on the business perspective, user perspective, or technical perspective … and you can move up and down the stack to zoom in or zoom out … but the main point is to show how the bits and pieces should fit together.  The power of a reference architecture is that it creates a shared mental model for the architecture and design and it can help you identify the key decisions and key risks early on.  This helps you both shape a skeleton solution as well as identify what you need to prototype, especially in terms of cross-cutting concerns, or tracer-bullets.  From an agile perspective, the Reference Architecture complements the system metaphor and it helps you identify potential areas to spike on.  Here are a few examples …

    One of my favorite reference architecture examples is the reference architecture from the ESB Toolkit.


    Another of my favorite reference architectures is the reference architecture for the PetShop Sample Application:


    One approach I like to use for sharing reference architectures is what I call Application Scenarios or Scenarios and Solutions.  It’s a whiteboard sketch of the end-to-end solution.  Here is an example:


    Another of my favorite approaches is to use what I refer to as Application Patterns.  It’s like the Application Scenarios, but I overlay patterns on top.  Here is an example:




    The real key of reference architectures is that they help you explore the thinking and design at a higher-level before getting lost in the weeds.  Getting lost in the weeds is a common problem with reference implementations.  That’s why it’s helpful when they include a reference to their corresponding reference architecture.

    The best combinations I find for nailing a problem space include a reference model + reference architecture + reference implementation.

  • J.D. Meier's Blog

    Change is Good


    "All projects experience changing requirements.  Traditional projects view this as bad.  Agile projects embrace it."  -- Steven Thomas, BBC

    Kelley Hunsberger writes about embracing scope creep, rather than fight it in her article “Change is Good”, in PM Network.

    According to Hunsberger, scope creep can create three key opportunities:

    1. Clients can figure out exactly what they want - clients figure out what they really want through the process
    2. The project team discovers a thing or two - the technical team is figuring out what works and what doesn't.
    3. Flexibility pays off - the ability to react to something late in the cycle is a competitive advantage.

    In my experience, this tends to be true, especially for knowledge work or where the work is not well known.  Change is a good thing, especially when it means acting on windows of opportunity, and delivering more value, in a timely way.  Customers tend to embrace the change when they are involved throughout the process.

    My favorite point in the article is about shaping scope as you go -- "With every sprint or iteration in agile, you are adding more clarity to the project's scope and reacting to it.  But just because you are changing the scope of a project doesn't mean you are adding more scope to it."

  • J.D. Meier's Blog

    Test-Driven Product Design


    One way to drive more effective product design is to start with scenarios.  One way to think of this is “Persona-based scenarios with goals.”  You can use the scenarios as test cases.  The scenarios can help you evaluate the design and they can help you evaluate implementation.  Simply put, “Can the persona or user perform the particular scenario effectively?”  You can then use criteria to evaluate.

    It’s test-driven product design.

    You can imagine how you can start with key themes and then break those down into more specific groups or frames. You end up with unit tests for experiences or scenarios and you can evaluate key things.  For example, if you were doing a competitive assessment, you might evaluate against the following criteria:

    • Complexity
    • Time to implement
    • Out of the box experience
    • Compliance with best practice

    The frames approach is a common approach for how platform competitive assessments are performed.  That’s why we adopted it as an approach for how we do prescriptive guidance … it’s a proven practice for mapping out the problem domain within a given domain or space.

    Example Scenarios Map
    This is an example of mapping out core scenarios, in this case, developer scenarios for source control:


    Example of Sub-Scenarios
    This is an example of elaborating the core Branch/Label/Merge scenarios above:


    There are many ways to gather, organize and use scenarios.  In the end, what’s important is that you have the user scenarios validated with the actual users, and that you use them as a hub to bring together the customer, the developers, and the testers.

    The beauty is that you can re-use the scenarios, whether it’s to explain your product, write documentation, or create prescriptive guidance.

  • J.D. Meier's Blog

    Evaluation Criteria Example


    I often find myself sharing examples of evaluation criteria in the prescriptive guidance space.  Here are some examples of criteria from one of my favorite platform assessments:

    • Best practice compliance. For a given analysis topic, to what degree did the platform permit implementation of best practices? Factors influencing best practice compliance include transparent integration (the default behavior enforces best practices automatically), user-assist features in the IDE, and degree of clarity of configuration.
    • Implementation complexity. How difficult was it for the developer to implement the desired feature? Factors influencing implementation complexity include the ease of use of the feature (as implemented in a tool), amount and length of code (if any was needed) Quality of documentation and sample code . How appropriate was the documentation? If examples were supplied with the documentation, were they sufficient to illustrate the concept, and did they exhibit best practices?
    • Developer competence. How skilled did the developer need to be in order to implement the security feature? To ensure an apples-to-apples comparison, prior knowledge of the tools platform is not assumed.
    • Time to implement. How long did it take to implement the desired feature or behavior?
    • The search cost. How long did it take for the user to find information on how to use the feature? Was the information shipped with the product or was it found externally on a vendor website or via search engine?
    • The implementation time. How long did it take, after knowledge assimilation, to configure or code the platform to implement correct behaviors?
  • J.D. Meier's Blog

    Scenario Scoreboards for Testing Your Product Success


    Here is an example of a simple, but surprisingly effective way to test your product success. Around patterns & practices, a few of us affectionately called this a “consumer reports” view.  Whether your product is prescriptive guidance or code, the concept is the same – you’re testing your product against user scenarios.

    To create a Scenario Scoreboard, simply put together a matrix of scenarios. Next, add criteria. Next, test against the scenarios and rate the criteria.  Note – There are two keys to making this successful: 1) have a useful collection of scenarios, and 2) get agreement on the criteria.  You want agreement on the criteria so that people can stand behind the results.  Tuning your criteria can help you tune your product success.  You’re basically creating a feedback loop to measure the success of your product against user scenarios.

    Example of a Scenario Scoreboard
    What’s important in the example is the simple frame:  scenarios and criteria.   The scenarios are grouped into buckets.


    Scenarios / Tasks


    Best Practice Compliance

    Implementation Complexity

    Implementer Competence

    Time to Implement


    • How to push peak loads to the cloud to reduce the size of an on premise data center.
    • How to decide if you application is right for the cloud (on-premise vs. cloud, advantages/disadvantages)
    • How to run your own VM in the cloud.
    • How to run an on-premise app in the cloud.
    • How to create a small-to-medium Web app.
    • How to create a large Web application.
    • How to create a parallel processing application.
    • How to store blog data for an on premise application.

    Arch / Design

    • How to structure your application.
    • How to partition based on latency.
    • How to scale horizontally.
    • How to scale vertically.
    • How to manage state.
    • How to design for Hybrid  (i.e. part of the application runs on premise, part in the cloud)

    Auditing and Logging

    • How to log information.
    • How to throttle your logging.
    • How to determine your log destination
    • How to view logs


    • How to authenticate callers.
    • How to perform single sign on (Federation).
    • How to build an STS.
    • How to identify callers.
    • How to manage personally identifying information / sensitive data in the cloud. 


    • How to use roles to protect resources.
    • How to leverage claims.
    • How to turn your application into a claims aware application.
    • How to turn claims into roles.


    • How to use local storage.
    • How to leverage a distributed cache.
    • How to swap out cache providers.
    • How to cache data effectively.
    • How to expire the cache.


    • How to cache configuration data.
    • How to decide what settings you should use.

    Data Access

    • How to design an extensible schema that will never need to be updated.
    • How to choose a partition key for different entities.
    • How not to get too much data into one partition.
    • How to repartition your live data.
    • How to load initial/domain data.
    • How to do BI in the cloud.

    Monitoring / Health

    • How to monitor web roles.
    • How to monitor worker roles.
    • How to alert/alarm.

    Performance and Scalability

    • How to simulate load tests.
    • How to compare blog storage against local files.
    • How to measure performance against CRUD.
    • How to do capacity planning.
    • How to access/view Performance Counters


    • How to design statelessness.


    • How to decide which storage to use.
    • How to organize your containers and blobs efficiently.
    • How to track/retrieve additional information/properties about blobs
    • How to authorize access to containers/blobs


    • How to roll back.
    • How to update multiple pieces of data at the same time.
    • How to implement 2-phase commit.
    • How to lock effectively.

    Worker Model

    • How to schedule work.
    • How to group different types of work.
    • How to communicate between different types of worker roles.
    • How to determine the number of worker roles.
    • How to determine if multiple threads should be used


    • How to design for asynchronous work.
    • How to design for integration (custom cloud applications / finished services / on premise / ESB.


    • How to deploy seamlessly with no downtime
    • How to architect your application to allow data schema deployment to happen independent from app deployment

    Ratings for the Evaluation Criteria
    Here are some examples of ratings for the criteria:

    Rating Category


    Best Practice Compliance Ratings

    1. Not possible
    2. Developer implements
    3. Developer extends
    4. Wizard
    5. Transparent

    Implementation Complexity Ratings

    1. Large amount of code
    2. Medium amount of code
    3. Small amount of code
    4. Wizard +
    5. Wizard

    Quality of Documentation and Sample Code Ratings

    1. Incorrect or inaccurate
    2. Vague or Incomplete
    3. Adequate
    4. Suitable
    5. Best Practice Documentation

    Developer/Administrator Competence Ratings

    1. Expert (5+ years of experience
    2. Expert/intermediate (3-5 years of experience)
    3. Intermediate
    4. Intermediate/novice
    5. Novice (0-1 years of experience)

    Time to Implement

    1. High (More than 4 hours)
    2. Medium to High (1 to 4 hours)
    3. Medium (16-60 minutes)
    4. Low to Medium  (6-15 minutes )
    5. Low (5 minutes or less )

    Additional Resources

    My Related Posts

  • J.D. Meier's Blog

    Product Success Frame for High Customer Impact


    What proven practices have you seen are vital behaviors that significantly contribute to customer success? …

    That’s a common question I get, having spent the bulk of my time at Microsoft in patterns & practices.  In fact, that’s a question the Windows Azure team asked me last Summer, as a way to boil down my lessons learned from patterns & practices and turn the insight into action.

    Let me first set the stage that this information is primarily what contributes to a product’s success aimed at “developers.”

    Banging on Products from Multiple Angles Helps You See the Good, the Bad, and the Ugly
    I’ve had a chance to see the good, the bad, and the ugly in terms of our products and how they land with customers.  I’ve participated in many dog-fooding exercises, supportability reviews, platform evaluations, etc., so I‘ve learned what to look for.  Because I’ve worked across so many products and technologies, I’ve had the chance to see what success patterns, as well as anti-patterns, show up time and again.   In fact, one of the things I often do is cross-pollinate the best practices that I see across various product teams.

    As an aside, before I joined patterns & practices, I worked in Microsoft Developer Support, which means I was on the receiving end of customer pain, and I learned how to walk a product from a usability and supportability standpoint, as well as learn many of the supportability (and “un-supportability”) patterns.

    A Quick Sampling of Product Success Patterns … 
    Here is a quick example to light up the idea of how some teams set the state for product success.  For example, the ASP.NET team drove significant improvements into their platform early on through eating their own dog food and performing application building exercises. This created a lot of empathy for customers and customer scenarios. Having “Blue Books” or “Platform Playbooks” for security and performance helped win significant accounts, as well as create a glide-path for customers coming from the Java world. The QuickStart for ASP.NET with it’s amazing set of “Common Tasks” helped many, many developers get up and running with the platform in a simple way. Having a set of common baseline architectures and deployment patterns helped us show customers how to make the platform work for their scenarios in a proven and repeatable way.

    Some Products are Destined for Success 
    To share what I’ve learned, I’ve created a simple frame that encapsulates some of the things that I’ve seen make a key difference. Creating prescriptive guidance has always been a combination of creating a “driver’s guide,” test driving the product against customer scenarios, finding effective solutions and workarounds, and improving the story around qualities, such as security or performance. During the process, I’ve found that some products are destined for success and have a strong customer adoption story out of the gate, while others face an uphill battle or never really succeed.

    Sadly, I can easily see products that will fail, right up front too.

    Product Success Frame
    Here is the frame I’ve been using for sharing some of the most important product success patterns. 


    It needs some iterations, but it’s been useful so far for putting some key success patterns into buckets.  The table below shares some examples of what would fall under these buckets.  After the table, I’ve provide some visual examples to help illustrate.



    Mental Models

    How to picture, think about, and talk about the problem space.

    • A Language for the Space (“Domain Model” / “Folksonomy” )
    • Application Scenarios (Common Patterns)
    • Canonical Architecture
    • Customer Solution Stacks (common combos of product and technologies)
    • Deployment Patterns
    • Frame (Lens for looking at the space, what’s in, what’s out)
    • Hot Spots (Top Areas of Pain or Opportunity)
    • Pattern Language (Shared vocabulary for the key concepts)

    Prescriptive Guidance

    Sharing and scaling expertise, including driver’s guides and proven practices.


    “Train-the-Trainer” material for wide-spread adoption and viral expertise.

    • Architecture Kit
    • Case Studies         
    • Demos
    • Offerings (MCS / Service SKUs)   
    • Roadmap  
    • Rude Q&A            
    • Slides        
    • Train-the-Trainer 
    • Webcasts / Podcasts


    • Capabilities Matrix
    • Competitive Studies


    Knowing your unique value and where you stand in the market or how you relate.

    • Capabilities Matrix
    • Competitive Studies

    Building for the customer and with the customer to co-create a better future, as well as simplifying the user experience, and making it easy to find all the blocks.


    Assume bad things happen to good people and making it easy to fall into the pit of success or get back to a successful state, or avoid falling off the cliff in the first place.

    • Dog-fooding
    • Fault-Tree Model
    • Supportability Review
    • Supportability Whitepaper


    Know the touch points and the constellation of channels where users interact with your stuff, along with the user experiences for each of those channels.

    • 3rd Party / Partner Sites
    • Community Site (Home)
    • Dev Centers
    • Forums
    • Subscriptions   


    • Customer Proof Points
    • Product Support Reviews (“BillG Reviews”)
    • SEO Analysis and Data
    • Usability Studies
    The Network

    Get the network on your side, from a tribe of raving fans, and closer followers, to a wider community base.

    • 5 Pillar Customers (Reference examples and champions)
    • Blogger Team
    • CAT (Customer Advisory Team) Team (“SQL CAT”)
    • Champs (Internal / External)
    • Community PM
    • Insiders (“ASP.NET Insiders”)
    • MVPs
    • Product Support / Escalation Team
    • Rangers (“TFS Rangers”)

    A Quick Tour of Examples …
    The following is a quick visual tour of some of the common things that help customers make the most of the product.

    Application Scenarios and Solutions Example
    Application Scenarios and Solutions are a quick sketch of how to solve an end-to-end problem, along with key information on how to prototype the solution and test whether the solution will work for your scenario.


    Canonical Application Architecture Example
    A canonical application architecture helps customer see how to put the building block technologies together into an ideal pattern.


    CAT “Customer Advisory Team” Teams
    Customer Advisory Teams site between the product and the customer and they help address the patterns of customer problems through prescriptive guidance and hands-on support.  They can also provide in-depth product feedback because they see the patterns and practices of large sets of customers, against specific scenarios and solutions.

    • Focused team that connects the customer scenarios to the product team.
    • Strong engineering team with a solution focus.
    • Solves customer problems (with a by-product of code and content re-usable assets.)
    • Provides actionable product feedback to the product teams.

    For an example, see the SQL CAT Team.

    Catalog of Solution Assets Example
    When you build out a catalog of solution assets, it’s a proven practice to have a set of content types.   This helps users know what to expect in your catalog.  This also helps you streamline your efforts for populating your catalog.  The key is to focus on a small set of high ROI content types.  For example, a common pattern is to focus on code samples, how tos, videos, and tutorials.


    Customer Proof Points
    Customer Proof points are simply verbatums and scores on a slide from a customer to help show impact.  The verbatums provide qualitative and the scores provide quantitative.  The two key numbers to see are overall satisfaction and a change in confidence in the product, tool, or platform.  


    Deployment Patterns
    Deployment Patterns show how the common ways that the application is physically distributed.  This can help you very quickly see the end in mind.


    Feature Set Example
    Having your feature set at a glance, helps users quickly see all the dials, knobs, switches at a glance.  Having the features at a glance is also an easy way to help your users learn the scope of your product.  You can also use the features at a glance as one way for organizing, driving, and prioritizing your documentation.  This, in conjunction with a scenarios map is a powerful combination.


    Hot Spots for Architecture
    Hot Spots are basically a heat map of common pain points or key engineering decisions.  They help you quickly see the forest from the trees in a given domain.  For example, in a typical application, some of the cross-cutting concerns are auditing and logging, authentication, authorization, data access, exception management, etc.  Knowing the Hot Spots helps inform you as an product designer or engineering, by helping inform you where to invest more energy.


    Hot Spots for Security Example
    You can think of Hot Spots as a lens and you can overlay or focus on a particular topic, such as security, and highlight just those Hot Spots.


    Hot Spots for Performance Example
    Here is an example of bubbling up common performance Hot Spots for a Web application.


    How Tos
    How Tos provide step-by-step instructions for performing a task or solving a problem.  When done well, they are among the most valued content because they directly map to user challenges, scenarios, and tasks.


    See Security How Tos for an example of a How Tos collection.

    Scenario Frames / Maps Example
    Scenario Maps are an easy way to gather and organize all the user scenarios in a meaningful way.  Scenarios put requirements into context by showing what a particular user would try to accomplish.  A collection of scenarios acts as a map that helps you see the landscape of your product, from both the engineering and the user view.


    Scenario Scoreboard Example
    A Scenario Scoreboard is a simple way to evaluate the effectiveness of your product against the user scenarios.  You simply add evaluation criteria and rate each scenario against the products, tools, and platform.


    QuickStarts (Simple Starts for Common Tasks)
    QuickStarts are a way to share a quick map of common tasks, along with examples and step-by-step guidance.


    See example at - http://quickstart.developerfusion.co.uk/QuickStart/howto/

    My Related Posts

  • J.D. Meier's Blog

    Anu on Getting Results the Agile Way


    “Productivity is never an accident. It is always the result of a commitment to excellence, intelligent planning, and focused effort.” -- Paul J. Meyer

    Anutthara Bharadwaj, a Program Manager on the Microsoft Visual Studio team shares her experience on adopting the Agile Results system in her post, Getting Results the Agile Way.  In her story, Anu writes how she went from being overwhelmed to on top of her game by adopting three core practices:

    1. The Rule of 3
    2. Monday Vision, Daily Outcome, and Friday Reflection
    3. Hot Spots

    I like her concrete examples.  In her case, she uses One Note to implement the system.   That’s the power of the Agile Results system.  It’s a principle-based system so you can use whatever tools works best for you for adopting the practices.  (I’ve used everything from pen and paper, whiteboards, Evernote, Outlook, One Note, simple text files, etc.)

    Small changes in your day, add up to big changes in life.  I’ve had the chance first-hand to watch Anu transform and it’s been an amazing journey.

    Stop by and check out Anu’s post on Getting Results the Agile Way.

  • J.D. Meier's Blog

    Time Management Tips #9 - Pair Up



    What's the best way to do it?


    Pair up.

    Time management tips #9 is pair up.  Paring up simply means find somebody that will work with you on something, rather than go it alone.   When you pair up, you create a team of capabilities and you learn how to love the things you might otherwise hate.  Worst case, you at least make doing what you don’t enjoy, more fun.  Best case, you find a new passion for something you didn’t know you had.

    We all have things to do that we're not great at, or slow us down.  Maybe it's because we don't have talent for it.  Maybe it's because we hate doing it.  Maybe it's because we just don't know a few tricks of the trade. (Sadly, I find the that it’s missing the tricks of the trade, that holds us back the most … and learning the tricks, actually unleashes a passion in us, because we no longer suck at it … it’s such a chicken and an egg scenario time and time again.)

    Chances are you know somebody who is great at whatever it is that you need to do, or at least better than you.  Just because you might hate to do something, doesn't mean that somebody else does not live for it.  One person's trash is another's treasure.  And that's a good thing. 

    Pairing up is the fastest way to transfer tribal knowledge.  It’s visceral.  You *feel* it.  You immerse yourself in it.  You get to see how somebody that likes doing this activity, actually goes about it.  It's your chance to learn everything from the mindset they have, to the questions they ask, to the short-cuts they use, or how they make it fun.

    One of my favorite phrases at work is, "Show me how."

    So many experts love to show and share how they do their magic.  It puts them in their element.  Sometimes they will genuinely want to help you succeed.  Other times, it's just so they can show off.  Either way, it doesn't matter.  What matters is that you make the most of it.

    One of the best pairing situations is where you find a "workout buddy" for work.  Maybe you are good at doing slides, and maybe they are good at technical details.  When you pair up, you can both look good, and you both have something to gain.

    Pairing works best when it's a mutual gain, so it's always helpful to bring something to the table.  Sometimes, all you bring to the table is appreciation for their amazing skill, and sometimes that is enough.

    Another great pattern for pairing is if you are a "starter" -- you like to start things, but you aren't a strong "finisher."  A strong "starter" and "finisher" pair is like a dynamic duo in action that amplify each other's success.  One's strength is another's weakness, and your goal is to build a mini-team of capabilities over a one-man band.

    It's not just effective, it's strategic.  By doing what you do best, and supplementing where you are not, you maximize your ability to make things happen in the most effective way, while staying true to you.

    In 30 Days of Getting Results, you can use the time management exercises to be a more effective starter or finisher and get exponential results on a daily and weekly basis.  You can also find more time management tips in my book, Getting Results the Agile Way, and on Getting Results.com

    You Might Also Like

  • J.D. Meier's Blog

    Embrace the Effort and Expand What You’re Capable Of


    I wrote a post about how to embrace the effort.   Effort is something I knew very well, and it's helped me differentiate in many scenarios.

    It's easy to downplay the benefit of effort, especially because you aren’t rewarded for effort, you’re rewarded for results.  I never got an A for effort (although I did get an E.)

    But here's the catch:  YOU have to reward yourself for your own effort.  And just because you don't get the results you wanted, you still need to acknowledge and appreciate your own effort.  It’s critical to your long-term success.

    Effort really is an essential ingredient of your personal greatness.  Sure, you can luck into success some of the time, and talent can get you so far, but effort is the difference that makes the difference, and it’s the maker of more consistent success.  Effort is also the key to making more meaning in your life, and it's an integral part of the path of fulfillment.  Yeah, fulfillment happens more when we give our best, where we have our best to give, on a meaningful mission.  Giving your best takes effort, and meaningful missions are always filled with challenges.  That’s why in life … it’s the journey AND the destination (and sometimes the journey is all we’ve got.)

    It's wise advice that we should focus on what we control, and let the rest go.  One of the toughest lessons in life is that we can't control everything … and many times, the results are out of our hands.   Sure, we get to influence, but the bigger the challenge, the less we control how the cards will fall. 

    But what do we always control?  The effort that we put in.  That’s the difference maker in our lives.

    If you're not getting the results you want in work or life, take a look at the effort you are putting in.  If you aren't putting in the effort required, try adding some effort to see if that makes the difference.  In fact, embrace the effort.  Effort is what expands what we're capable of.  Feel the effort, and feel your growth.

    When effort is not the trick, it's often a matter of strategy.  Working harder isn't always the answer (though sometimes it is.)  A lot of times it's working smarter.  In many cases, the answer is "AND" ... it’s about working smarter AND working harder.  (What a powerful combo.)

    The beauty is that well-applied effort, often pays off.

    And if you acknowledge and reward yourself along the way for the effort you put in, that always pays off.

    Check out embrace the effort, and put the power of effort on your side.

  • J.D. Meier's Blog

    Time Management Tips # 10 - Set Limits



    I hate quotas.  For me, I'm about quality, not quantity.  And yet quotas have consistently helped me get the ball rolling, or find out what I'm capable of.

    Time management tips # 10 – set limits.  When we set a quota, we have a target.  It helps turn a goal into something we can count.  And when we can count it, we build momentum.

    In my early days of Microsoft, my manager set a limit that I needed to write two Knowledge Base articles per month.  I did that, and more.  Way more.  It turned out to be a big deal.  Before that limit, I didn't think I could do any or would ever do any.

    A few years back, I set a limit that my posts would be no longer than six inches (yeah, that sounds like a weird size limit, but I wanted to fill no more than where the gray box on my blog faded to white.)  My blog ended up in the top 50 blogs on MSDN, of more than 5,000 blogs, and my readership grew exponentially that month.  The reason I set the size limit is because my original limit was "write no more than 20 minutes."  The problem is, when I'm in my execution mode, I write fast, and my posts were getting really long, even if I only wrote for 20 minutes.

    Setting limits in time, size, or quantity can help you in so many ways.  Especially, if getting started is tough.  One great way to start, is simply to ask, "What's one thing I can do today towards XYZ?"  Limits also help us avoid from getting overwhelmed or bogged down.  If we’re feeling heavy or overburdened, start chopping at limits until your load feels lighter.

    Here are some example of some limits you can try:

    1. Write one blog post each day.
    2. Spend a maximum of 20 minutes each day on XYZ.
    3. Spend a minimum of 30 minutes on exercise every other day.
    4. Spend 30 days on XYZ.
    5. Read three books this month.
    6. Cut the time of your XYZ routine in half.
    7. Ship one phone app this month.
    8. Ship one eBook this month.
    9. Start one blog this month.
    10. Spend no more than 30 minutes on email a day.

    Once you set a limit, you suddenly get resourceful in findings new ways to optimize, or new ways to make it happen.  When there is no limit, it's tough to optimize because you don't know when you are done.

    While I'm a fan of quality, the trick is to first "flow some water through the pipe" so you can tune, prune, and improve it.

    If you're feeling rusty, try setting little limits to bootstrap what you're capable of.

    In 30 Days of Getting Results, you can use the time management exercises to be more effective and get exponential results on a daily and weekly basis.  You can also find more time management tips in my book, Getting Results the Agile Way, and on Getting Results.com

    You Might Also Like

  • J.D. Meier's Blog

    Time Management Tips # 11 - 30 Day Sprints


    Do you have something that you've been wanting to learn, but just don't have the time?  Do you have an area at work that you struggle with?  Do you dabble in too many things at once, and never make real progress?

    Enter 30 Day Sprints.

    Time management tip # 11 is 30 Day Sprints30 Day Sprints let you try something out for 30 days and make progress.  30 Day Sprints also give you a way to cycle through something new each month.   It’s a great way to embrace continuous learning.  Each month you can add something new to your portfolio of skills, so at the end of the day, you can have 12 big changes under your belt.

    I adopted 30 Day Improvement Sprints several years ago to deal with a couple of challenges:

    1. I needed a way to really focus.
    2. I needed a way to make significant change.
    3. I needed a consistent way to make space for new things in my life.

    What I learned is that committing to 30 days of improvement in a focused area, is easier to swallow than changing for life.  However, improving an area for 30 days, is actually life changing.

    With 30 days, persistence and time are on my side.  It's a big enough time box that I can try different techniques, while building proficiency.  Using 30 days makes working through hurdles easier too.  A lot of the hurdles I hit in my first week, are gone by week 2.  Little improvements each day, add up quickly.  I look back on how many things I tried for a week and stopped thinking I hadn't made progress.  The trick was, I didn't get to week 2 or week 3 to see my results.

    That last point is a big deal.  When you stick with something for more than two weeks, you get over the humps and hurdles that hold you back.  It's like chipping away at the stone, and sometimes the breakthroughs don't happen until you're a few weeks in.

    This is also a powerful way to add habits or change a habit.  Why?  Because you can do something small today.  And tomorrow you can do another small thing.  You can keep little commitments with yourself.  You can glide your way into your habit, versus run out of steam.  If you’ve ever been gung-ho for a week, and then fizzled out, 30 Day Sprints can be your answer.

    As we turn the page to a new month, pick a focus for the month, and make it your 30 Day Sprint.

    In 30 Days of Getting Results, you can use the time management exercises to get exponential results on a daily and weekly basis.  You can also find more time management tips in my book, Getting Results the Agile Way, and on Getting Results.com

    You Might Also Like

  • J.D. Meier's Blog

    Time Management Tips # 12 - Do Something Small


    Sometimes small is the best way to make progress.  In fact, sometimes it's the only way.

    If you don't have time to do something big, do something small.  Don't make a major production out of it, don't make a mountain out of a molehill.  Chunk it down.  It's a skill you can practice daily. 

    What's one small thing you could do … today?

  • J.D. Meier's Blog

    Time Management Tips #13 - Just Start


    Sometimes getting started is the hardest part.  In fact, sometimes the start takes more effort than the work:

    "It is always the start that requires the greatest effort." -- James Cash Penney (Yeah, the guy that started J.C. Penney’s)

    If you don't know where to start, then start with something small.

    Be a fire-starter ... use your little victories for kindling.

    How do you get started? 

    Just start.

  • J.D. Meier's Blog

    7 Practices for More Effective Meetings


    Here are seven practices I’ve experienced that worked well with meetings:

    1. Let a person finish their point
    2. Answer the question asked.
    3. Say what you mean, mean what you say.
    4. No leading questions or asking questions you know the answer to (see #3)
    5. Answer the question simply, and only elaborate if asked (this saves on long answers to the wrong questions or misunderstandings.)
    6. Make it safe to explore an idea and play out a thought -- help each other express/understand/be understood.
    7. Ask questions at the end – this builds momentum.

    It’s really about momentum … we can spiral up or spiral down.  Energy is our best asset to spend on the right things.

    On #7 -- Any time I've seen meetings have momentum (and I can think of multiple vignettes), it’s when somebody put their thoughts out on the table first, without being sliced and diced along the way.  I also think of examples, where somebody finishes painting the broad strokes of their picture  ... and we get the bigger picture, before needling at the fine points, and fracturing great ideas in the making … or at least getting the bird’s-eye view before chasing the rabbit down the hole.

    When we practice #7, it builds trust, people are heard and understood, and people will be less long-winded, and defensive, etc.

    Bonus --- Have a skilled facilitator, manage the shot clock, set time for things (timebox), take decisive actions, and have a parking lot to put things.

  • J.D. Meier's Blog

    Why We Feel Unproductive


    “If you want something done, ask a busy person to do it. The more things you do, the more you can do." -- Lucille Ball”

    I was reading Scott Hanselman's post on Productivity vs. Guilt and Self-Loathing.  In his post, Scott shares what he does when he feels unproductive.  If you know Scott, he's the opposite of unproductive.  So the question then is ...

    Why do we sometimes feel unproductive?

    I played with this question on my way to work, and then a few dots connected.

    We See the Work
    I connected the dots when I was surprised by a few people that said they didn’t really see all the work ahead.  They were working on a few things, but there was not an amazing forest of challenges and opportunities ahead of them.   Instead, it was just a tree here or there.  It baffled me, but then it clicked.  Not everybody looks to see the forest.

    As a Program Manager, I'm constantly breaking work down.  I need to map out paths from A to B. I'm constantly sorting massive lists of work to be done.  I'm always looking at the system.  I need to find the bottlenecks in our system and ecosystem and unblock them.  I need to orchestrate people to bring out their best.  I need to foresee and anticipate humps and hurdles and have a game plan to get around them.

    It's not that the job of a Program Manager is never done (It isn't BTW.)  It's that some people see the task at hand, while others see the bigger map.

    Any idea that comes my way, I have to start breaking it down into experiences, scenarios, features, requirements, timelines, milestones, etc.  I always see the work.

    Some people don't "see the work."  I've run into this pattern multiple times, where somebody looks like they have nothing to do.  In their mind they don't.  Nobody told them to do anything.  They aren't a self-starter.  If nothing is assigned to them, then there's nothing to do.  For others, they are looking for work, but they can't see the work.  They haven't done work-breakdown-structures, or iteration planning, or any sort of planning, so they just aren't familiar with how to look for work ... and more importantly, they don’t know how to identify meaningful and game-changing work.

    When you see the bigger map, it can feel like people are re-arranging deck chairs on the Titanic.  Your job then becomes to educate people on the why, the what, and the goals of the work, so people can put the deck chairs down, and re-focus their efforts.

    So when I measure myself against the work to be done, I always fall short.  When I get to the top of the mountain, I see more mountains.

    The solution?   Set milestones, identity tests for success, and stop to smell the roses.  Look back on achievements, to balance always looking ahead.

    We Have Ideas
    When you constantly flow ideas, you are brutally aware of missed opportunities, and worse, missed windows of opportunity.  The backlog of ideas just keeps growing, and, it's not a shortage of good or even great ideas, there is a shortage of execution.

    It's OK for bad ideas or lesser ideas to die a slow death, but it's a real shame when the game changers die due to lack of love.

    It's amazing how many ideas can flow when you know how to debottleneck your mind.  When I learned that Thomas Edison had an idea quota, I thought that was interesting.  You get what you measure, and you get more of what you focus on.  When I learned how to clear my head by dumping my state, and to capture ideas with a thought catcher, my speed of ideas outpaced my execution by a long shot.  As a Program Manager, I'm skilled in making things happen and going from idea to done ... but my pace of ideas outpaced what was possible within time, resource, and budget constraints.

    The solution?  Focus on the whitelist of great ideas, versus the blacklist ... Hit more windows of opportunity, ruthlessly prioritize, trade bad, good, or great for oustanding, and really focus on wins ... three wins for the day, three wins for the week, three wins for the month, three wins for the year. 

    We Feel the Impact
    This one is tough.  When you know what's possible from excellent execution, and when you know the power of productivity, it's actually painful when opportunities slip through your fingers.  When you can step into the future and you know how the world could be a better place, and yet at the same time, you know that without the right things happening, it's not going to happen ... it's tough.

    When you know that a lack of execution or lack of effective productivity will translate into businesses going under, or people losing their jobs, or evil winning the day, it's tough to rest.  On the flip side, when you know that giving a little more, and then a little more, can create powerful transformation, it's tough not to fight the good fight, and march onward and updward.

    Again, it can be tough to stop and smell the roses, and it can feel like the weight of the world on your shoulders.

    We Don't Always Keep Score
    We learn in school to focus on what we got wrong, not what we got right.  We forget to ask the simple questions like:

    - What's on my "Done" list?
    - What were my wins for the day?
    - What were my wins for the week?
    - What were my wins for the month?
    - What were my wins for the year?

    One of the people I mentor asked me if it was important to keep her "Done" list.  (A "Done" list is simply a list of things you completed during the day.)  I said, "Absolutely.  It's a reminder of what you achieved during the day.  And you can balance it against your three wins that you identified at the top of your list."

    The idea here is that, as simple as it sounds, a little progress can go a long way toward feeling productive, and feeling fulfilled.  Little lists help, even as simple as having a "Done" list for your day.

    We Have to Trim the Tree
    Periodically, we have to “Trim the Tree.”  We have to put the bags down, and start with a clean slate.  We need a fresh look, and a fresh perspective.  We need to recharge and renew.  We need to let our “mighty mounds of work-to-be-done”, crumble and fall, so we can build better, more meaningful mounds.  

    The reality is that time changes what’s important, and if we keep carrying the weight forward, it holds up back or holds us down.  We have to cut the dead wood.

    I like using a “Trim the Tree” metaphor because I think of trimming branches, beyond just leaves.  My goal is always to get back to the essential that matters … here and now … and to shape what will matter … so that the way forward is sustainable, inspiring, and lifts us in ways we know are possible.

    The goal – at the end of the day – is this …

    You need to be who you want to be, and create the experiences you want to create. 

    Your best strategy for that is to follow your personal strategy for work and life, including your vision, mission, and values, and playing to your strengths, and differentiating through your unique experience, capabilities, and approach.  We also know three paths of happiness you can follow:

    1. The Pleasant Life – Do more stuff that feels good now.
    2. The Good Life – Spend more time in your values.
    3. The Meaningful Life – Follow your personal path of fulfillment by doing great service for the greater good, giving your best where you have your best to give, and living your vision, mission, and values.

    When you combine strategy with your productivity, you help not only life your meaningful life, but you help lift the life of others, by bringing your unique value to the world.  Or, to put it another way, it’s a great way to build skills to pay the bills and lead a better life.

    I’ve baked many of these strategies and techniques from hard lessons learned in the most challenging scenarios into a simple system for meaningful results.  It’s Agile Results, and it’s introduced in my book, Getting Results the Agile Way.   You can read it free online, or get Getting Results the Agile Way on Kindle and take it with you wherever you go.

  • J.D. Meier's Blog

    Time Management Tips #14 - Dump Your State



    When it comes to time management, one of the most common questions I get is, “How do you dump your state?”  Meaning, how do you dump what's on your mind to a place you trust, and how do you pick up where you left off?

    Time management tips #14 is dump your state.  Dumping your state helps you pick back up where you left off, and it frees your mind to focus on the tasks at hand.  It also helps you move up the stack.  After all, if your mind is filled with little unclosed loops, you are not at your most resourceful and creative best.

    When you have baggage of the brain, it's tough to focus. Your mind is busy circling back on the loops it hasn't closed.  It's also buzzing endlessly in the background to remind you of the things you should not forget.  All the mental chatter gets in the way of you having peace of mind, clarity of thought, and focused attention ... right here, right now.

    That's one scenario of why dumping your state matters.

    Another scenario where dumping your state matters is when we want to pick up from where we left off.  We spend all day working on a problem, building up state, but then we can't finish, so we have to park if for the day.  The problem is we want to be able to pick back up the next day, from where we left off.  Worse, sometimes we can't pick up back up the next day, and then all the state we built up starts to rot on the shelf of our minds, or decays in some place that we may never find again.

    So what can you do?

    It's very simple, and I call it brain dumps or "Session Dumps."  To do a “Session Dump”, just dump what's on your mind, down onto paper or onto a page, using your favorite system.  For me, sometimes this is an email that where I will dump my whiteboard fast, or I use Onenote to dump, or I use EverNote to dump plain text.  In most scenarios, I have notepad open on my desktop, and I constantly dump to it ... so instead of little insights or actions floating in my head, they are jotted down to where I can see and organize them.

    It might seem like an endless list in your mind, but you’ll be surprised that the more you dump, the less it is.  It gets faster too.   And thinking on paper is powerful.   When you see the list in front of you, you may very quickly realize what you can let go, and what you really need to hold on to.

    Here's the real trick though.  Since I do this daily, I found that the best approach is to simply "dump state" to a clean sheet each day, and to name it the current date.  For example, for today, I would title my Session Dump as follows:


    Naming my Session Dump by date means I never need to figure out a good title, and by keeping all of my dumps in one folder, it's easy for me to always find them.  I use that simple format because I can easily flip through in sequence.

    I have to let a lot of things go, so I can focus on the best opportunities and challenges that lie before me.  Time is always changing what’s important.  Having a rapid way to dump state or pick up where I left off is a big deal.  Now I never have to wonder where I dumped straggling ideas, or things that were percolating on my mind.

    At the end of the day, dump your state before you go home and see how much it frees you up.

    For free, self-paced modules on time management training, check out 30 Days of Getting Results.

    You Might Also Like

  • J.D. Meier's Blog

    Time Management Tips #15 - Make Lists for Action



    Every time you have to remember what’s next to do, you waste your time.  You've heard of "paper shuffling."  This is like "thought shuffling."  You spend a lot of time shuffling your thoughts around, but not actually doing anything.

    Enter stage right … the power of lists.

    Time management tips #15 is make lists for action.  Use lists to organize and take more effective action.  Lists are your friend.  They help you organize your thoughts and ideas into action.  Pilots use checklists.  Sure they know what to do, but they also know that having the checklist helps free up their mind (specifically, their prefontal cortex).  Teams use inspection lists to drive quality, share processes, and share work.  Companies large and small use checklists for quality control and streamlining performance.

    You can use lists to streamline yourself, improve your own quality, and simplify your work.

    When you make your lists, test them against effectiveness.  Keep them as simple as possible, but make sure they help you.  Never become a slave to your list.  If your list gets too big, start a new one and carry the good forward.  Let things slough off.

    Here are some of the most useful lists to have, when it comes to organizing your work and guiding your action:

    1. TODO for Today.  List your goals and tasks for the day.  Tip – Add your Three Wins for Today at the top)
    2. TODO for the Week.  List your goals and tasks for the week.  Tip – Add your Three Wins for the Week at the top)
    3. List of Projects.  List of the actual projects you are working on.  Give them a name.
    4. One List Per Project.  Have one list for each project to dump outcomes, goals, insights, actions.  This gives you one place to look.
    5. Backlog.  All the stuff you think you need to do.  Tip – Organize this by A-Z so you can quickly scan and find duplicates, and it forces you to name things better.  Name your work so you can refer to it, talk about, and think about it more effectively.
    6. Ideas.  Your nifty ideas to change the world, or your world, or whatever.
    7. Irritation List.  List of the things that bug you.  Get it out of your head, and down onto paper.

    Another useful list is a quick list of the steps for a given task.  This can help you stay on track, or remember where you are, or easily find the next step.  The trick is not to over do this, or over-engineer your steps, or worse, forget to be flexible in your approach.  Focus on the goal, but stay flexible in how you achieve it.

    Goals are always your guide.

    Use lists to organize your work, organize your actions, and simplify your work and life.

    For free, self-paced modules on time management training , check out 30 Days of Getting Results, and for more time management tips check out Getting Results.com.

    You Might Also Like

  • J.D. Meier's Blog

    Time Management Tips #19 - Just Finish


    Sometimes you need to Just Start.  Other times, you need to Just Finish.

    One of the best ways never to finish something, is to spread it out over time.  Time changes what's important.  People lose interest.  Changes of heart happen along the way.  Spreading things over time or pushing them out is a great way to kill projects.

    Open items, open loops, and unfinished tasks compound the problem.  The more unfinished work there is, the more task switching, and context switching you do.  Now you're spending more time switching between things, trying to pick up where you left off, and losing momentum.

    This is how backlogs grow and great ideas die.  This is how people that "do" become people that "don't."

    Time management tips #19 is just finish.  If you have a bunch of open work, start closing it down.  Swarm it.  Overwhelm your open items with brute force.  Set deadlines:
    - Today, I clear my desk.
    - Today, I decide on A, B, or C and run with it.
    - Today, I close the loop.
    - Today, I solve it.
    - Today, I clear my backlog.

    If you want to finish something, then “own” it and drive it.  To finish requires ruthless prioritization.  It requires relentless focus.  It requires putting your full force on the 20% of the things that deliver 80% of the value.  It requires deciding on an outcome and plowing through until you are done.

    Stop taking on more, until you finish what's on your plate.  If you want to take on more, then finish more.  The more you finish, the better you get.

    The more you finish, the more you will trust yourself to actually complete things.

    The more you finish, the more others will trust you to actually take things on.

    The more you finish, the more you build your momentum for great results.

    For time management skills , check out 30 Days of Getting Results, and for a time management system check out Agile Results at Getting Results.com.

    You Might Also Like

  • J.D. Meier's Blog

    Should 30 Days of Getting Results Be Flashcards or a List of Lessons?



    I’m testing the user experience again at 30 Days of Getting Results.   It’s worth it and I want to get it right, since I have a lot more people asking me about training now for Agile Results.

    If you can take the new experience for a test drive, and give me feedback on whether you like the new experience over the original, that helps a ton.  (Unfortunately, I don’t have live A/B testing.  If you don’t know the original experience, imagine a simple white page with a list of lessons on the side, and I have a screenshot below.)

    If you don’t know Agile Results or what 30 Days of Getting Results is all about, here’s the scoop …
    30 Days of Getting Results is a serious (and free) self-paced time management training course.  It full of time management skills and productivity skills..   You’ll learn how to triple your productivity (actually, you can 10X it, but I’m trying to under-promise and over-deliver.)   Teams across Microsoft are using Agile Results to master time management, improve their productivity, and drive more value … better, faster, cheaper … and most importantly, more meaningful.

    What’s the secret?  …
    Oh nothing … just more than ten years of testing, experimenting, and refining across many, many people and teams to create a simple and flexible system that could stand up to some of the most rigorous scenarios and requirements.   Agile Results is holistic and it rides above the top of things.  It’s a synergy of proven practices that help you work on the right things, at the right time, the right way, with the right energy.  It’s about flowing value and focusing on the essential things that matter, using the 80/20 rule.  It’s about playing to your strengths, teaming up to achieve more, and hitting more windows of opportunity.  It’s about lighting a fire so you can blaze a trail through your workload, breakthrough barriers, and jump the hurdles that stand in your way. 

    It’s about thinking in threes:  three wins for the day, three wins for the week, three wins for the month, three wins for the year.  It’s about adding Power Hours to your week so you can whip out more achievements in less time, with greater ease.  It’s about adding more Creative Hours to your week so you can find and flow more creative solutions, invent your next best thing, and unleash the productive artist in you.   It’s about recharging and renewing with skill.  It also puts science on your side, including the best learnings from positive psychology and sports psychology to unleash your best performance.  It’s also a synthesis of proven practices for motivation, directing your focus with skill, prioritizing with decisive action, and making your moments count.  For the softer side, it’s an East meets West productivity system, where you will do less, achieve more, and enjoy more effortless ways of producing outstanding results.

    With that in mind, here are the two experiences I am testing …

    Experience A:  Flashcards
    Experience A is currently live at 30DaysOfGettingResults.com


    With this experience, you see a set of visuals that represent each lesson.  When you click a lesson, that lesson expands and shows you the outcome, the insight, and the action for the day.  The upside with Experience A is that it’s interactive and it reinforces the idea that you don’t have to go through the lessons sequentially.  Each lesson is self-contained.  While the overall training is designed with a flow in mind, you can dive into whatever lesson you want.

    Experience B: Simple List of Lessons


    With this experience, it’s pretty straight-forward – it’s a list of lessons down a side-bar, and each page is a lesson.  In fact, that’s why I liked this experience.  It’s very simple, very minimal, and no confusion.  Just pick a day, click and go.   While the upside is simplicity, the potential downside is boring.   That said, boring and functional is fine by me, but I need to hear from more users, on what they prefer.

    A few people told me last week that they wanted a more visually appealing site and more interactivity.  Ironically, I had spent a lot of money on the pictures for each page, but it just wasn’t obvious with the original landing page (Experience B above.)

    I do think that Experience A does really showcase the images and it does encourage click-through.   I find myself clicking the lessons and exploring a lot more.  I know the novelty wears off, but maybe novelty is all I need if it helps you learn the 30 lessons.

  • J.D. Meier's Blog

    3 Calendar Reminders for Agile Results


    Agile Results is an simple system of proven practices to focus, set goals, find your motivation, improve your productivity, master time management, and achieve work-life balance.   It’s a way to get your game on.

    This is a simple way to add Agile Results to your calendar.  It’s the best way to “easily do”, and “remember to do”, Agile Results:

    1. Add a Monday Vision Reminder (My Three Wins for the Week)
    2. Add a Daily Outcomes Reminder (My Three Wins for the Day)
    3. Add a Friday Reflection Reminder (3 Things Going Well, 3 Things to Improve)

    That’s it.  It takes under a minute.

    Simply create a recurring appointment for Monday Vision on Mondays, create a recurring Daily Outcomes reminder for each day of the week, and create a recurring Friday Reflection reminder on Friday.

    In the Monday Vision reminder, I would add the following question to the body:

    “What are your three wins for the week?”  (Write them down.)

    In the Daily Outcomes reminder, I would add the following question to the body:

    “What are your three wins for TODAY?”

    In the Friday Reflection reminder, I would add the following questions to the body:

    “What are three things going well?”

    “What are three things to improve?”

    The beauty of this approach is that it helps you build the muscle, until it’s a habit.  You can also add notes to each of your appointment that help you remember how to do it well, or you can add your learnings.  For example, let’s say on Friday Reflection you realize that you are biting off more than you can chew each week, then in your Monday Vision, add a simple self-check question – “Are you biting off more than you can chew?”

    The possibilities are endless, and the power is yours.

  • J.D. Meier's Blog

    How To Read Blogs More Effectively


    Too many blogs, not enough ROI?   Is your backlog of posts to be read, wearing you down?

    No more.

    I’ll keep this post short or it defeats the purpose, so let’s cut right to the chase …

    There is a secret to reading blogs more effectively, and it’s not reading faster.  It’s adding a strategic lens on top, so that you get back the most value, from the reading time you put in.   The strategic lens helps you trim your blog list down to size, and focus on the blogs that give you the most bang for your buck.

    I’ll summarize the steps to do so, but I’ve elaborated here at How To Read Blogs More Effectively

    The short answer is:

    1. Identify your strategic objectives.
    2. Build your portfolio.
    3. Review your portfolio.

    If you want the details, and to improve your ROI from blogs for life, check out:

    How To Read Blogs More Effectively

    You’ll even see how I pare down Michael Hyatt’s blog posts and turn insight into action.  (Note – and if you really just want to know how to read faster, I’ve included a link to that too.)

    Minimally, you’ll learn another approach for ruthless prioritization of the blogs you read.  Best case, I help you find more “priceless” blogs on the Web.  Happy hunting.

Page 39 of 44 (1,077 items) «3738394041»