Taylor Life in Other Word

When, while the lovely valley teems with vapor around me, and the meridian sun strikes the upper surface of the impenetrable foliage of my trees, and but a few stray gleams steal into the inner sanctuary, I throw myself down among the tall grass by the trickling stream; and, as I lie close to the earth, a thousand unknown plants are noticed by me: when I hear the buzz of the little world among the stalks, and grow familiar with the countless indescribable forms of the insects and flies, then I feel the presence of the Almighty, who formed us in his own image, and the breath of that universal love which bears and sustains us, as it floats around us in an eternity of bliss; and then, my friend, when darkness overspreads my eyes, and heaven and earth seem to dwell in my soul and absorb its power, like the form of a beloved mistress, then I often think with longing, Oh, would I could describe these conceptions, could impress upon paper all that is living so full and warm within me, that it might be the mirror of my soul, as my soul is the mirror of the infinite God!

O my friend — but it is too much for my strength — I sink under the weight of the splendor of these visions! A wonderful serenity has taken possession of my entire soul, like these sweet mornings of spring which I enjoy with my whole heart. I am alone, and feel the charm of existence in this spot, which was created for the bliss of souls like mine.

I am so happy, my dear friend, so absorbed in the exquisite sense of mere tranquil existence, that I neglect my talents. I should be incapable of drawing a single stroke at the present moment; and yet I feel that I never was a greater artist than now.

When, while the lovely valley teems with vapor around me, and the meridian sun strikes the upper surface of the impenetrable foliage of my trees, and but a few stray gleams steal into the inner sanctuary, I throw myself down among the tall grass by the trickling stream; and, as I lie close to the earth, a thousand unknown plants are noticed by me: when I hear the buzz of the little world among the stalks, and grow familiar with the countless indescribable forms of the insects and flies, then I feel the presence of the Almighty, who formed us in his own image, and the breath of that universal love which bears and sustains us, as it floats around us in an eternity of bliss; and then, my friend, when darkness overspreads my eyes, and heaven and earth seem to dwell in my soul and absorb its power, like the form of a beloved mistress, then I often think with longing, Oh, would I could describe these conceptions, could impress upon paper all that is living so full and warm within me.



What is customer experience?
Customer experience (also known as CX) is defined by the interactions and experiences your customer has with your business throughout the entire customer journey, from first contact to becoming a happy and loyal customer.

CX is an integral part of Customer Relationship Management (CRM) and the reason why it’s important is because a customer who has a positive experience with a business is more likely to become a repeat and loyal customer.

In fact, according to a global CX study by Oracle found that 74% of senior executives believe that customer experience impacts the willingness of a customer to be a loyal advocate. If you want your customers to stay loyal, you have to invest in their experience!

7 ways to improve the customer experience
Let’s take a look at seven ways to create a great customer experience strategy to help you improve customer satisfaction, reduce churn and increase revenues – including examples.

  1. Create a clear customer experience vision
    The first step in your customer experience strategy is to have a clear customer-focused vision that you can communicate with your organization. The easiest way to define this vision is to create a set of statements that act as guiding principles.

For example, Zappos use their core family values and these values are embedded into their culture; which includes delivering wow through service, being humble and embracing change.

Once these principles are in place, they will drive the behavior of your organization. Every member of your team should know these principles by heart and they should be embedded into all areas of training and development.

  1. Understand who your customers are
    The next step in building upon these customer experience principles is to bring to life the different types of customers who deal with your customer support teams. If your organization is going to really understand customer needs and wants, then they need to be able to connect and empathize with the situations that your customers face.

One way to do this is to segment your customers and create personas (or customer profiles). Try to give each persona a name and personality. For example, Anne is 35 years old; she likes new technology and is tech savvy enough to follow a video tutorial on her own, whereas John (42 years old) needs to be able to follow clear instructions on a web page.

By creating personas, your customer support team can recognize who they are and understand them better. It’s also an important step in becoming truly customer centric.

  1. Create an emotional connection with your customers
    You’ve heard the phrase “it’s not what you say; it’s how you say it”?

Well, the best customer experiences are achieved when a member of your team creates an emotional connection with a customer.

One of the best examples of creating an emotional connection comes from Zappos:

When a customer was late on returning a pair of shoes due to her mother passing away. When Zappos found out what happened, they took care of the return shipping and had a courier pick up the shoes without cost. But, Zappos didn’t stop there. The next day, the customer arrived home to a bouquet of flowers with a note from the Zappos Customer Success team who sent their condolences.

Research by the Journal of Consumer Research has found that more than 50% of an experience is based on an emotion as emotions shape the attitudes that drive decisions.

Customers become loyal because they are emotionally attached and they remember how they feel when they use a product or service. A business that optimizes for an emotional connection outperforms competitors by 85% in sales growth.

And, according to a recent Harvard Business Review study titled “The New Science of Customer Emotions“, emotionally engaged customers are:

At least three times more likely to recommend your product or service
Three times(!) more likely to re-purchase
Less likely to shop around (44% said they rarely or never shop around)
Much less price sensitive (33% said they would need a discount of over 20% before they would defect).

  1. Capture customer feedback in real time
    How can you tell if you are delivering a WOW customer experience?

You need to ask – And ideally you do this by capturing feedback in real time.

Use live chat tools to have real time conversations and when done, send a follow up email to every customer using post-interaction surveys and similar customer experience tools.

Of course, it’s possible to make outbound sales calls to customers in order to gain more insightful feedback.

It’s also important to tie customer feedback to a specific customer support agent, which shows every team member the difference they are making to the business.

  1. Use a quality framework for development of your team
    By following the steps above, you now know what customers think about the quality of your service compared to the customer experience principles you have defined. The next step is to identify the training needs for each individual member of your customer support team.

Many organizations assess the quality of phone and email communication, however, a quality framework takes this assessment one step further by scheduling and tracking your teams development through coaching, eLearning and group training.

  1. Act upon regular employee feedback
    Most organizations have an annual survey process where they capture the overall feedback of your team; how engaged they are and the businesses ability to deliver an exceptional service.

But, what happens in the 11 months between these survey periods?

Usually, nothing happens. And this is where continuous employee feedback can play a role using tools that allow staff to share ideas on how to improve the customer experience and for managers to see how staff is feeling towards the business.

For example, using project management software or social media tools, you can create a closed environment where your organization can leave continuous feedback.

  1. Measure the ROI from delivering great customer experience
    And finally, how do you know if all this investment in your teams, process and technology are working and paying off?

The answer is in the business results.

Measuring customer experience is one of the biggest challenges faced by organizations, which is why many companies use the “Net Promoter Score” or NPS, which collects valuable information by asking a single straightforward question:


Native Mobile App Vs. Hybrid Mobile App

If you are thinking of developing a mobile app, an important decision is to decide whether you want to a native app or a hybrid one. Choosing to use native or hybrid mobile application is always the pain for everyone who wants to make their mobile apps.

From our experience working with mobile app development we have narrated following inputs which we feel will be useful for you make a decision.

Native apps are specific to a given mobile platform (iOS or Android) using the development tools and language that the respective platform supports (e.g., Xcode and Objective-C with iOS, Eclipse and Java with Android). With Native apps, you have complete control over features you want to implement in an app. In terms of overall performance which includes look and feel, using device features etc. Native app is best.

Hybrid apps makes it possible to embed HTML5 apps inside a thin native container, combining the elements of native and HTML5 apps. This write-once-run-anywhere approach to mobile development creates cross-platform mobile applications that work on multiple devices. While developers can create sophisticated apps with Hybridapp development platforms such as PhoneGap, some vital limitations remain at the time of this writing, specifically session management, secure offline storage, and access to native device functionality (camera, calendar, geolocation, etc.)

Each option has it’s own pros and cons. Based on project requirement and matching the platform competencies you can take decision. Following are the detailed information about each option which will give you better ideas about what to expect from Native or Hybrid platforms for mobile app development.


In a nutshell, native apps provide the best usability, the best features, and the best overall mobile experience. Both, with iPhone App or Android App, There are some things you only get with native apps like;

Additional Device Accesses: There are common device features such as Multi touch, double taps, pinch-spread, and other compound UI gestures which are only available with native apps.

Fast graphics API: The native platform gives you the fastest graphics, which may not be a big deal if you’re showing a static screen with only a few elements, or a very big deal if you’re using a lot of data and require a fast refresh.

Fluid animation: related to the fast graphics API is the ability to have fluid animation. This is especially important in gaming, highly interactive reporting, or intensely computational algorithms for transforming photos and sounds.

Built-in components: The camera, address book, geolocation, and other features native to the device can be seamlessly integrated into mobile apps. Another important built-in components is encrypted storage, but more about that later.

Ease of use: The native platform is what people are accustomed to, and so when you add that familiarity with all of the native features they expect, you have an app that’s just plain easier to use.

Documentations: There are over 2500 books alone for iOS and Android development, with many more articles, blog posts, and detailed technical threads on sites like StackOverflow.

Native apps are usually developed using an integrated development environment (IDE). IDEs provide tools for building debugging, project management, version control, and other tools professional developers need. While iOS and Android apps are developed using different IDEs and languages, there’s a lot of parity in the development environments, and there’s not much reason to delve into the differences. Simply, you use the tools required by the device.

You need these tools because native apps are more difficult to develop. Likewise, the level of experience required is higher than other development scenarios, you don’t just cut and paste Objective-C and expect it to work. Indeed, the technological know-how of your development team is an important consideration. If you’re a professional developer, you don’t have to be sold on proven APIs and frameworks, painless special effects through established components, or the benefits of having your code all in one place. Let’s face it, today a skilled native iOS or Android developer is a rock star, and can fulfill rock star demands.

While we’ve touched on native apps from a development perspective, there’s also the more important perspective: the end user. When you’re looking for an app, you’ll find it in the store. When you start the app, it fires up immediately. When you use the app, you get fast performance, consistent platform look and feel. When your app needs an update, it tells you so. Native apps give you everything you’d expect from the company that built your device, as if it were simply meant to be.


We define hybrid a web app that is wrapped inside a thin native container that provides access to native platform features. PhoneGap is an example of the most popular container for creating hybrid mobile apps. Existing web developers that have become gurus at optimizing JavaScript, pushing CSS to create beautiful layouts, and writing compliant HTML code that works on any platform can now create sophisticated mobile applications that don’t sacrifice the cool native capabilities. In certain circumstances, native developers can write plugins for tasks like image processing, but in cases like this, the devil is in the details.

On iOS, the embedded web browser or the UIWebView is not identical to the Safari browser. While the differences are minor, they can cause debugging headaches. That’s why it pays off to invest in popular frameworks that have addressed all of the limitations.
You know that native apps are installed on the device and you might be wondering if hybrid apps store their files on the device or on a server? Yes. In fact there are two ways to implement a hybrid app.

Local – You can package HTML and JavaScript code inside the mobile application binary, in a manner similar to the structure of a native application. In this scenario you use REST APIs to move data back and forth between the device and the cloud.

Server – Alternatively you can implement the full web application from the server (with optional caching for better performance), simply using the container as a thin shell over the UIWebview.

Netflix has a really cool app that uses the same code base for running the UI on all devices: tablets, phones, smart TVs, DVD players, refrigerators, and cars. While most people have no idea, nor care, how the app is implemented, you’ll be interested to know they can change the interface on the fly or conduct A/B testing to determine the optimal user interactions. The guts of decoding and streaming videos are delegated to the native layer for best performance, so it’s a fast, seemingly native app, that really does provide the best of both worlds.


Native app is definitely better if you need device features like camera, notification and gesture etc. Native app is better if you want your app to work when there is no connectivity. Although In-browser caching is available but it is limited. Speed: Native is better in speed. Maintenance: Multiple native code maintenance difficult more complex and expensive method while Hybrid is easier to manage.

If platform independence is important then you should go with Hybrid over native. If you want user experience to be consistent with the platform then native is better option. This does not mean that Hybrid cannot have good UI. But native app will make more like actual platform.


Design Thinking.

Design thinking is all about finding solutions that respond to human needs and user feedback. People, not technology, are the drivers of innovation, so an essential part of the process involves stepping into the user’s shoes and building genuine empathy for your target audience.

  1. Collaboration

The aim of design thinking is to pool a diverse variety of perspectives and ideas; this is what leads to innovation! Design thinking encourages collaboration between heterogeneous, multidisciplinary teams which may not typically work together.

  1. Ideation

Design thinking is a solution-based framework, so the focus is on coming up with as many ideas and potential solutions as possible. Ideation is both a core design thinking principle and a step in the design thinking process. The ideation step is a designated judgment-free zone where participants are encouraged to focus on the quantity of ideas, rather than the quality.

  1. Experimentation and iteration

It’s not just about coming up with ideas; it’s about turning them into prototypes, testing them, and making changes based on user feedback. Design thinking is an iterative approach, so be prepared to repeat certain steps in the process as you uncover flaws and shortcomings in the early versions of your proposed solution.

  1. A bias towards action

Design thinking is an extremely hands-on approach to problem-solving favoring action over discussion. Instead of hypothesizing about what your users want, design thinking encourages you to get out there and engage with them face-to-face. Rather than talking about potential solutions, you’ll turn them into tangible prototypes and test them in real-world contexts.



How to make sprint retrospective meetings more effective

What is a sprint retrospective?
A sprint retrospective, typically the last step involved in Scrum methodology, is a meeting scheduled at the end of a sprint. The team, including the Scrum master and product owner, reviews what went well during the sprint and what could be improved in an effort to continuously analyze and optimize the process.

You spend a lot of time in meetings. On average, anywhere from 23% to 37% of your time is spent in meetings. If you are a Scrum master or in middle management, it’s possible that you spend up to 50% of your time attending meetings.

If you’re going to spend a large chunk of your time in meetings, you should always make sure that the meetings you plan—especially one as important as a sprint retrospective—are productive and efficient. In fact, a good sprint retrospective idea may be to discuss how many meetings the team attends, how long meetings should last, how productive those meetings are, and how you can make meetings more productive.

This article includes some fun ideas that you can easily incorporate to run your sprint retrospective meeting more effectively and efficiently.

What is covered in a sprint retrospective?
Simply put, the Scrum retrospective meeting lets you analyze your process in the previous sprint and create a plan for improvements in the next. So what do you discuss in a sprint retrospective? Really anything that affects how the team creates the product is open to scrutiny and discussion, including processes, practices, meetings, environment, and so on.

The meeting is meant to give the Scrum team the opportunity to ask and address questions such as:

What did we do right in the previous sprint?
What did we do wrong in the previous sprint?
What should we start doing in the next sprint?
What should we stop doing in the next sprint?
What can we do to improve productivity?
When is a sprint retrospective meeting held?
Your sprint retrospective meeting should be held after your sprint review and before the next sprint planning session. Sandwiching the retrospective between the two, you and your team can most effectively discuss what worked in your previous sprint, as well as what can be improved, while your previous sprint is fresh in your mind. You can also discuss what commitments your team can make to ensure the next sprint is successful, based on data and observations from your previous sprint.

Who should attend sprint retrospective meetings?
All members of the Scrum team—Scrum master, product owner, and developers—should attend the retrospective meeting. The meeting should provide an environment where the team members feel safe to share honest feedback on what’s going well and what could be improved and to participate in a discussion of what needs to change with clearly defined action items.

How long should a sprint retrospective take?
The length of your sprint retrospective meeting may vary slightly based on the length of your sprint and the retrospective technique you employ. Sprints lasting a month usually require no more than a three-hour sprint retrospective. Shorter sprints will likely require less time to dissect (and as we’ll mention below, we recommend keeping the meeting as short as you can). Scrum masters should allow for ample time to discuss and collaborate between team members while also making sure that the meeting remains productive.

Sprint review vs. sprint retrospective
While the purpose of the sprint retrospective is to help teams reflect on the previous sprint in order to improve processes, the sprint review’s purpose is a little different. The sprint review is a two-part meeting in which the Scrum master, the development team, the product owner, and other stakeholders present their progress to the customer. The team’s progress is carefully measured against the commitments made at the beginning of the sprint, and the customer is given a chance to offer input on the progress made.

How to run a sprint retrospective effectively
Studies show that a major complaint of the Agile methodology is the perception that there are too many meetings. Of course, for some people, one meeting per week is too many. What can you do to keep the team from thinking that a sprint retrospective is more than just another meeting?

Keep it simple

You are not going to solve all your problems in one meeting, so don’t try to. Instead, boil the discussion down to the few questions we listed earlier:

What do we need to stop doing?
What do we need to start doing?
What do we need to continue doing?
The idea is to engage your team by encouraging them to quickly identify where improvements can be made and what actions can be taken to make those improvements. For example, maybe your team has the problem of going over the 15 minutes scheduled for the daily standup meetings—you can easily fix this by making sure your meetings always start and end on time.

Whatever you discuss in a sprint retrospective, make sure you are inviting participation, documenting suggestions, and voting to determine which actions to take.

Keep it short

Meetings take time, and time means money. According to a 2014 report, over $25 million is wasted per day on meetings—$37 billion per year. In addition, it can take up to 20 minutes for employees to focus on their work again after an interruption such as a meeting or incoming email. Keeping your meetings short and to the point can go a long way to keeping costs down and productivity up.

You’ve scheduled your sprint retrospective for one hour (or three), but does that mean that you have to use the whole hour? It’s okay to end meetings early.

Stay focused

Your retrospective meeting should not be a social gathering. Stick to your agenda to stay focused. Create a retrospective meeting agenda that can help members of your team who seem to spend more time on unrelated tangents than on topic.

Change things up a bit

Meetings can be really boring, and bored team members are less likely to participate. In fact, bored employees are more likely to read email, work on other projects, or fall asleep. Regularly scheduled meetings, such as a retrospective, can become repetitive. If you see eyes glazing over and you keep getting the same answers to the same questions, you need to change things up a bit to get team members involved.

You can also try to add games or other fun activities to liven up the room and get your team more excited about participating in another retrospective meeting. See the examples below.